Wessel, Jason wrote:
>> I must note that the whole b/p mechanism has been a mess
>>-- there are these {set|remove}_breakpoint() methods that
>>never get called by KGDB and there are overridable
>>kgdb_arch_{set|remove}_breakpoint() functions which get
>>actually called. The situation was with h/w breakpoints was
>>even worse -- both direct and indirect calls were in use... :-/
>> I'd suggest to remove those s/w breakpoint related indirect calls.
> Does that imply that you feel the HW breakpoint support is ok then? I
> did try to make some effort to clean up the HW breakpoint access at
> least to the point that it is really arch specific.
I had no time for actual testing yet, of course -- but at least it looks
saner that it was. And you've said it's even working :-)
> I thought that intent for the sw breakpoint routines was that an arch
> could override it if needed.
And it does, via overriding kgdb_arch_{set|remove}_breakpoint(). But the
indirect {set|remove}_breakpoint() calls are never used.
> Jason.
WBR, Sergei
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
