Organization of breakpoint locations

[Thomas Neumann]

Daniel Jacobowitz schrieb:
> sometime this year.  But I think we can add a sequence number to
> bp_location's just like breakpoints have.
>   
and in fact a separate number seems to be needed, as the breakpoint
number is unknown (zero) when the breakpoint location is created. I did
not investigate this further and  just added a number to bp_location.
> I'd like GDB to be able to manage huge breakpoint lists; I'm just
> warning you that a lot more work will have to be done first ;-)
>   
ok, here is a first step: attached is small patch that stores the
breakpoint locations in a splay instead of a list. The patch is fairly
straight forward: mostly one compare function for splay-tree.c and a
number of iterator functions to simplify the access macros. It even
survived a make check. I hope this patch motivates someone to fix the
scalability issues with breakpoints ;-)


Thomas

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: breakpointsinsplay.patch
URL: <http://sourceware.org/pipermail/gdb/attachments/20070220/fb92c38f/attachment.ksh>