From: Christopher Faylor <me@cgf.cx>
To: gdb@sourceware.org
Subject: Re: How does solib handline shared library unloads?
Date: Tue, 01 Nov 2005 16:20:00 -0000 [thread overview]
Message-ID: <20051101162025.GA16212@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20051101151212.GA27574@nevyn.them.org>
On Tue, Nov 01, 2005 at 10:12:12AM -0500, Daniel Jacobowitz wrote:
>On Tue, Nov 01, 2005 at 09:40:32AM -0500, Christopher Faylor wrote:
>> On Tue, Nov 01, 2005 at 08:51:42AM -0500, Daniel Jacobowitz wrote:
>> >On Tue, Nov 01, 2005 at 08:45:47AM -0500, Christopher Faylor wrote:
>> >>Is this handled as part of the so breakpoint stuff? I was trying to
>> >>avoid implementing that but I will if I have to.
>> >
>> >Well, that's how we get to solib_add for svr4 targets; but it should
>> >work to get there off an explicit DLL unload event, anyway. I think.
>>
>> Yeah, that's what I did but I think that the more I make the windows
>> target work like linux, the less chance there will be that it will get
>> out of sync with ongoing development.
>>
>> So, I might eventually just try to make this work more like linux.
>
>Well, there's other targets which provide explicit unload notification
>(HP/UX; perhaps Symbian someday)...
Cygwin sets TARGET_WAITKIND_LOADED when a DLL is loaded but I don't see
any corresponding TARGET_WAITKIND_UNLOADED. It doesn't look like
TARGET_WAITKIND_LOADED calls solib_add, though.
cgf
next prev parent reply other threads:[~2005-11-01 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 5:39 Christopher Faylor
2005-11-01 6:59 ` Mark Kettenis
2005-11-01 13:45 ` Christopher Faylor
2005-11-01 13:51 ` Daniel Jacobowitz
2005-11-01 14:40 ` Christopher Faylor
2005-11-01 15:12 ` Daniel Jacobowitz
2005-11-01 16:20 ` Christopher Faylor [this message]
2005-11-01 16:24 ` Daniel Jacobowitz
2005-11-01 18:24 ` Mark Kettenis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051101162025.GA16212@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox