Re: Debugging

[Günther Rapp <guenther rapp-informatik de>]

If you have the sources of the callback routines

you get put a debugging a output line at the begin to the callback
routines
an only print it if wanted testing an environment variable or a file
like this
   if ( getenv("DEBUG_ON") && fprintf(stderr,"entering callback 1\n");

Having debugged all your code you can use   sed to go through all files
and deleting the line or you compile with a   
#if DEBUG_ON
fprintf(stderr,"entering callback 1\n");
#endif

mfg 
günther

Russell Shaw schrieb:
> Archit Baweja wrote:
> > Well if you wrote he program, you should know which callbacks are called
> > when something is clicked, or activated etc.
>
> But i didn't write it, and it's too complicated to follow
> without gdb at runtime.
>
> > You can also put a breakpoint in the callback, and do a backtrace
> > to see what functions were called leading up to callback.
>
> Breakpointing every function takes forever for gdb to do.
>
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

-- 
R=I+S  Rapp Informatik Systeme GmbH
       Rosenbühlstr. 24
       D-89182 Bernstadt
       Tel:  +49 (0)7348-7755
       Fax:  +49 (0)7348-6086
E-MAIL  mailto: guenther rapp-informatik de
WEB             www.rapp-informatik.de

Attachment: guenther.vcf
Description: Visitenkarte für Günther Rapp