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] |
Think PIE.
I am, in fact, thinking about pie. Oh, you mean PIE...
For our purposes, both new executable loaded and new shlib loaded are the same event - there's been an objfile_loaded event. There's no reason to differentiate them.
The new inferior event is orthogonal, and far more low level.
I don't see how "new inferior" is any lower level than "new object".
In any case, thread-db wants to initialize when these two conditions are true: (A) The inferior is running and (B) The thread library has been loaded
So using an inferior created hook makes perfect sense to me...
-> inferior_created -> thread-db -> solib loaded -> objfile mapped -> thread-db
-> inferior_created -> objfile mapped -> thread-db -> shlib loaded -> objfile mapped -> thread-db
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |