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] |
Last time this was discussed the observer was identified as the correct mechanim for hooking this in. That's why I'm currently overhauling that code.
Ok. I forget many things, but I think this is news to me.
I hadn't seen the "observer" code before; I now see it's a simple facility for running a list multiple hooks previously registered, so this is today's preferred form of adding a new hook. Two questions remain for me:
What is the new hook or hooks you plan to add? i.e., will it be a single "look freshly at address space" hook, or separate hooks for "attached", "exec'd", "opened core", etc? It matters little, unless we anticipate future different situations that would also qualify as "look freshly at address space" situations but aren't one of the three I listed.
Where is the right place to install our observer? My inclination is to add linux-tdep.c to all the Linux targets as my strawman patch does, and have an _initialize_linux_tdep function that registers the observers. Is that what you are thinking as well?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |