On Mon, 2005-10-31 at 01:12 -0600, Ben Wing wrote:
Stephen J. Turnbull wrote:
>>>>>>"Ulrich" == Ulrich Müller <um(a)gregory.sax.de>
> Ulrich> #4 0x0814a739 in byte_marker_position ()
>Gah. Stripped executable (no information about arguments or source
>file). That means we're just going to have to do a code review on
>everything in that neighborhood (we can't even count on that being the
>right function; it could be an inline or even in a following static
>function). That's going to take time.
Ulrich, can you compile xemacs yourself and see if you can reproduce? i
don't see anything obvious in the stack trace you've sent that would
help localize the problem.
Modern rpm based distributions tend to strip all binaries, yes, but also
place the stripped stuff and associated source files into eg. a
"xemacs-debuginfo" or "xemacs-debug" package that can be separately
installed alongside the main "xemacs" package and gdb automatically
knows how to look from these "detached" symbol blobs. I don't know if
SuSE does that, but if they do, that should help in getting a more
useful C backtrace, no need to compile from sources oneself.