* Re: shared library events
2006-12-11 19:50 ` Daniel Jacobowitz
@ 2006-12-11 21:18 ` Jim Ingham
0 siblings, 0 replies; 3+ messages in thread
From: Jim Ingham @ 2006-12-11 21:18 UTC (permalink / raw)
To: dsign; +Cc: gdb
We implemented a "file-sharedlibrary-info" command to return
information about all the currently loaded shared libraries, but we
don't really use that. It turned out that stopping the GUI to query
for shared library information for every shared library event slowed
down the UI, and didn't add any benefits. Except for resolving
breakpoints there wasn't anything we needed to do synchronously for
shared library loads, and that's all taken care of on the gdb side.
We also added asynchronous shared library load notifications.
Something like:
=shlibs-added,shlib-info=[num="4",name="Cocoa",kind="F",dyld-
addr="0x90f43000",reason="dyld",requested-state="Y",state="Y",path="/
System/Library/Frameworks/Cocoa.framework/Versions/A/
Cocoa",description="/System/Library/Frameworks/Cocoa.framework/
Versions/A/Cocoa",loaded_addr="0x90f43000",slide="0x0",prefix=""]
Some of this info (requested-state & state are specific to some tricks
we play to reduce the symbol footprint of all the libraries in X).
The Xcode can keep track of the libraries as they load and update it's
shared library display, without having to do a round trip with gdb.
Jim
On Dec 11, 2006, at 11:50 AM, Daniel Jacobowitz wrote:
> On Mon, Dec 11, 2006 at 10:13:15AM -0800, dsign wrote:
>> Is there any mi interface for handling shared library events?
>>
>> If there isn't any, I could implement one. Please, any suggestions
>> welcome.
>
> I recommend you check with Jim Ingham to see what Apple does about
> this, since I believe they've got something similar on their branch.
>
> --
> Daniel Jacobowitz
> CodeSourcery
^ permalink raw reply [flat|nested] 3+ messages in thread