This is the mail archive of the gdb@sourceware.org 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]

[RFC] STOP_UNKNOWN and BREAKPOINT_HIT in infrunc.c


Hi,

in infrun.c there is enum inferior_stop_reason with two elements

* STOP_UNKNOWN
* BREAKPOINT_HIT

which aren't used anywhere in GDB beside in print_stop_reason(...)

   case STOP_UNKNOWN:
     /* We don't deal with these cases from handle_inferior_event()
        yet. */
     break;

   case BREAKPOINT_HIT:
     /* We found a breakpoint. */
     /* For now print nothing. */
     break;


Do we need both of them? Maybe it's a good idea to keep STOP_UNKNOWN just in case there is some new behavior but BREAKPOINT_HIT isn't needed, I think.



Regards,
Markus

--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com



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