On Wed, 21 Aug 2002, Muli Ben-Yehuda wrote:
> On Wed, Aug 21, 2002 at 08:15:34AM +0300, Shlomi Fish wrote:
>
> > I don't understand why it should matter. gdb can analyze the stacks of
> > programs that were compiled without debugging symbols.
>
> What about frame pointers? I remember checking once, but I don't
> recall the outcome.
>
Re-compiling glib and gtk without -fomit-frame-pointers did make me able
to view the complete stack trace. Thanks.
Regards,
Shlomi Fish
> It's also possible that it's simply a bug in the code.
>
> > > If you compiled the application from source (I assume you did, not
> > > much point trying to debug it otherwise), the path of least resistance
> > > is to debug only the application code and treat its library calls as
> > > black boxes. That means figuring out what appliation code calls the
> > > functions above (or what gets called by them) and setting a break
> > > point there explicitly.
> >
> > Unfortunately, this is a GUI program and library calls call callbacks in
> > the application. I don't think I can afford to do that.
>
> Why not? put a breakpoint in the callback you want to debug.
> --
> calm down, it's *only* ones and zeros.
>
> http://syscalltrack.sf.net/
> http://vipe.technion.ac.il/~mulix/
>
----------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Home Page: http://t2.technion.ac.il/~shlomif/
Home E-mail: [EMAIL PROTECTED]
"Let's suppose you have a table with 2^n cups..."
"Wait a second - is n a natural number?"
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
