Re: RFC: hacky fix for PR 12406

Tom Tromey
2012-01-12T21:31:05Z

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> An idea that crossed my mind: Add a flag to each entry in our SO
Joel> list. Everytime we stop, we use that flag to determine which entries
Joel> are new. We can probably use something like the normal-stop hook to
Joel> set the flag just before giving the prompt back to the user. Would
Joel> that work? It would support the situation I mentioned above where
Joel> we get one breakpoint event for multiple shared libraries...

Thanks for the idea. I will give it a try.

Tom> [Inferior loaded library /lib64/ld-linux-x86-64.so.2]
Tom> Stopped due to shared library event

Gary> Could this be a separate option, trace-solib-events maybe? It seems
Gary> like this printing might also be useful when stop-on-solib-events is
Gary> off.

Gary> Also, as Jan said, it would be nice to have unload notifications too.

This comment inspired me to take another look at the whole problem.

I actually do not much like stop-on-solib-events. I think 'catch'
commands are better, because they offer the user more control: commands
at the stop point, "silent", conditions.

So now I am thinking that, while I may still add the notification in
some form, I will also resurrect "catch load" and "catch unload",
something like "catch load [REGEX] [if ...]"

Tom