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]



If this is just an internals issue, then toss a coin, it
doesn't matter.  But for the picture that we present to the
user, remember -- we always present a fictional picture that
hides most of the underlying details.  The unsophisticated
user thinks he is debugging his code -- not the underlying
machine.  If possible, he doesn't want to know eg. that
line seventeen has been broken into several locations and
intermixed with code from 3 other lines.  We're sometimes
forced to tell him anyway, but we don't if we can avoid it.

Yes, it is user visible (which is why people are also looking for a user-level command, different to "maint info break" and "info break", that displays both the logical and physical breakpoint).


With a GUI, I can see each logical breakpoint having an expand widget (correct technical term is?) that lets the user see (modify?) the underlying physical breakpoint list.

This is needed, as otherwize something apparently simple "break strcmp" could result in the user unknowingly setting 1000's of breakpoints.

enjoy,
Andrew



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