[cdt-debug-dev] Re: A couple debugger things. (fwd)

["Alain Magloire" <alain@xxxxxxx>]

This thread should probably be on this list.

----- Original Message -----
From: "Alain Magloire" <alain@xxxxxxx>
To: "Peter Graves" <pgraves@xxxxxxx>
Cc: "Mikhail Khodjaiants" <mikhailk@xxxxxxx>
Sent: Thursday, September 19, 2002 2:05 PM
Subject: Re: A couple debugger things.


> >
> In ICDIBreakpointManager.setLocationBreakpoint(int type..)
> type is described as :"type - - a combination of TEMPORARY and HARDWARE or
> 0" but it does not say where these 2 constants are defined
> (ICDIBreakpoint
> it turns out) A javadoc update may be usefull here.
>

PR.
I'll take care of this one later.

> >
> >
> Also, when setting break points, in gdb I can set a break point by just
> passing it a line number without a file (break 11, or in
> mi -break-insert -h
> 11) and it will set a break point at that line in the current source
> file.
> If I try to do the same thing through the cdi it will end up sending
> "-break-insert -h -- *0"    Is that the expected behaviour?
> >
> Since the file == null and the function == null, it went to the default case
> which is address and the address was initialize to 0.
>

A bug.  Can you PR, I will correct this.

>
>
> And thirdly.. If I create a new location with
> ICDIBreakpointManager.createLocation(null, "funcname", 0), then do a
> setLocationBreakpoint() with that location. If I then get the break point
> back from the breakpoint manager (getBreakpoints() call), and compare the
> two location with a something like
> breakpoint.getLocation.equals(originalLocation), the call will fail because
> the location returned from the break point contains the extra info gdb found
> (line numbers, addresses, and file name).  Should that work?
>

Good point.
the setLocationBreakpoint() returns a ICDILocationBreakpoint.getLocation()
This is the Location object you should use for the comparison.
But ... thinking of it, you are right,
I should reset the information send by gdb to the original Object Location.

Please PR.  I'll fix it.

BTW: If you have already have patches for some of the stuff, feel free
to send them to cdt-patches.