From: Daniel Jacobowitz <drow@false.org>
To: Gordon Prieur <Gordon.Prieur@Sun.COM>
Cc: gdb@sourceware.org
Subject: Re: stop-on-solib-events and Cygwin (or MinGW)
Date: Thu, 14 Feb 2008 17:09:00 -0000 [thread overview]
Message-ID: <20080214170852.GA3552@caradoc.them.org> (raw)
In-Reply-To: <47B473F8.5050401@sun.com>
On Thu, Feb 14, 2008 at 09:01:44AM -0800, Gordon Prieur wrote:
> Hi,
>
> I've just added support to the NetBeans gdb module for breakpoints
> set in shared libraries explicity dlopened (as apposed to shared libraries
> linked at link time). I'm using stop-on-solib-events to do this, and it
> works
> fine on both Solaris and Linux.
Why do you need to do this? i.e. what are you doing with breakpoints
that current versions of GDB don't handle for you? (There may be a
good reason, I'm just curious what it is.)
> However, if I set this property on Windows I don't get stopped after
> my dlopen/dlclose calls. Is there any way (on Windows) to make this
> feature work? The alternative is to provide a complete 2nd implementation
> for Windows (based on stopping in dlopen, calling "finish", and comparing
> info share from before and after). Since stack information isn't always
> reliable on Windows, I'm concerned this method won't be very reliable.
>
> Are there technical reasons why stop-on-solib-events doesn't work on
> Windows? Or is it just unimplemented on that platform? Would I see the
> same behavior on Vista?
It's just unimplemented. However, you might want to try a current CVS
snapshot. I think it should work now that Pedro switched win32 over
to XML-based libraries.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-14 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 17:02 Gordon Prieur
2008-02-14 17:09 ` Daniel Jacobowitz [this message]
2008-02-14 17:41 ` Gordon Prieur
2008-02-14 18:14 ` Daniel Jacobowitz
2008-02-14 18:58 ` Gordon Prieur
2008-02-14 19:05 ` Daniel Jacobowitz
2008-02-14 19:18 ` Vladimir Prus
2008-02-14 19:43 ` Eli Zaretskii
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=20080214170852.GA3552@caradoc.them.org \
--to=drow@false.org \
--cc=Gordon.Prieur@Sun.COM \
--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