(From the perspective of CDT...)

When debugging a Cygwin-built program, and we've told gdb to stop on shared
library events, the invocation (run) of the program produces a series of
stopped events because of library loads. But these events are absolutely bare.
Gdb gives no indication that the target stopped because of a library load.
Typically, such an indication comes in the form of a stream record that
accompanies the stopped event. Again, in this case, we get *nothing*. See the
attached gdb log. This represents all the activity from the beginning of the
session up to reaching main(). Note that getting to main() required hitting the
resume button three times (three library load events). Notice the bare *stopped
message and the lack of any stream records revealing the reason.


Here's what a normal stopped-for-library-load event looks like:


152-exec-continue
152^running
(gdb) 
~"Stopped due to shared library event\n"
Stopped due to shared library event
152*stopped,thread-id="1"

With this information, CDT is able to realize that the stop is because of a
shared library and auto-resume the target. Without the information, the user
just sees the program stopped for no apparent reason.