Messages in this thread | | | Date | Thu, 16 Jun 2005 16:40:19 -0400 | From | Daniel Jacobowitz <> | Subject | Re: problem with gdb back-traces on AMD64 (32 bit executables) |
| |
On Thu, Jun 16, 2005 at 11:07:46AM -0400, Wolfgang Wander wrote: > This is regarding a gdb problem regarding stack back-traces with > AMD64 and -m32 compiled executables. When the program receives > a signal inside a shared library of an m32 executable (or if > one attaches to such a program and it executes a shared library > function) back traces are useless. > > I'm sending this to the kernel list for two reasons: > > a) the gdb maintainers have not shown any interest in the issue, yet > ;-), maybe because of b) > b) the problem only affects 2.6 kernels, 2.4 kernels are fine.
It's not a kernel bug. Please try GDB CVS again, since HJ recently committed a related fix for x86_64 GDB.
-- Daniel Jacobowitz CodeSourcery, LLC - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |