This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFA: Breakpoint infrastructure cleanups [0/8]


Daniel Jacobowitz writes:
 > > I think 'info break' should list the addresses.  I don't know how this
 > > should fit into the MI format, but it ought to be MI that changes,
 > > rather than omitting useful behavior.
 > > 
 > > In my ideal world, you'd get an explanation for why each address was
 > > chosen, when it's not obvious:
 > > 
 > > (gdb) info break
 > > Num Type           Disp Enb Address    What
 > > 1   breakpoint     keep y   0x08048354 in foo::foo (in-charge) at hello.c:8
 > >                             0x08048364 in foo::foo (not-in-charge) at hello.c:8
 > > (gdb) 
 > 
 > Here's the problem that I see.
 > 
 > For foo::foo, there are two of these things.  Having them both in the
 > list would be nice.  Really nice.
 > 
 > For inline_accessor_fn there are 3.8 million.  In addition to needing
 > to do a whole lot of work on GDB internals before we could survive this
 > (memory usage; ptrace thrashing inserting and removing them; linked
 > lists of breakpoints; and that's just the beginning) this has some
 > severe user interface implications.  We don't want to print out all
 > those addresses by default!
 > 
 > I'm open to suggestions on how to deal with this.
 > 

There is already 'maint info break', how about extending that?  Would
you be able to distinguish between foo::foo breakpoints and inline
breakpoints so that they can be displayed on separate lists/commands?

elena



 > -- 
 > Daniel Jacobowitz
 > MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]