Re: [Anjuta-list] setting breakpoint

[Carlo Agrusti <carlo-ag libero it>]

Philipp Klaus Krause ha scritto lo scorso 20/05/2006 16:00:
> How can I set a breakpoint on a function?
> 
> I'm getting the following error message when running my program, how can
> I set a breakpoint on gdk_x_error?
> Is this possible with anjuta 1.2.4a (everything I see about breakpoints
> looks as if I can only set them in my own code, not in an external library)?
> 
> The error was 'BadColor (invalid Colormap parameter)'.
>   (Details: serial 296 error_code 12 request_code 1 minor_code 0)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error() function.)
> 

There is a menu entry (Debug->Breakpoints->Breakpoints...) which pop-ups
a window for breakpoint manipulation; in this window you can "Add" a new
pointer in a gdb-ish way (for instance by entering a line such as
"you_app.c:313"), but AFAIK there is no possibility to set an equivalent
of gdb command:

gdb> b function_name

I fear that you have to use plain gdb interface to debug a shared object
function *OR* you must first locate gdk_x_error in GDK source files and
use above procedure (provided that you have installed debug version of
GDK library on your system).

All the above for Anjuta-1.2.4; eagerly waiting for Anjuta-2 migrating
to Debian testing :-)