Re: [Bug: 21.5-b16] Close window crash
"Stephen J. Turnbull" <stephen(a)xemacs.org> wrote:
>>>>> "Jerry" == Jerry James
<james(a)xemacs.org> writes:
Jerry> Note that frame #4 should actually have fingered
Jerry> input-method-motif.c, line 134. However, the function call
Jerry> on that line has one argument FRAME_X_TEXT_WIDGET (f), and
Jerry> that's where the file and line number come from. Is that
Jerry> our fault, or is binutils/gcc/gdb insane?
I can confirm it's the toolchain. I had exactly the same problem with
gdb on Ghostscript, as well as really bizarre arguments in many stack
frames (eg, stack frame zero had one of its args == argv?!?)
Check this out from the GDB 6.0 release announcement:
------------------------------------------------------------------------
* New backtrace mechanism (includes DWARF 2 Call Frame Information).
DWARF 2's Call Frame Information makes available compiler generated
information that more exactly describes the program's run-time stack.
By using this information, GDB is able to provide more robust stack
backtraces.
The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
have been updated to use a new backtrace mechanism which includes
DWARF 2 CFI support.
------------------------------------------------------------------------
Maybe this problem will go away soon.
--
Jerry James
http://www.ittc.ku.edu/~james/