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 18:14:00 -0000 [thread overview]
Message-ID: <20080214181353.GA7518@caradoc.them.org> (raw)
In-Reply-To: <47B47D3B.8050708@sun.com>
On Thu, Feb 14, 2008 at 09:41:15AM -0800, Gordon Prieur wrote:
> Its customer driven. In NetBeans, breakpoints persist outside of a gdb
> session.
> The simplified scenario I'm using in my test cases contains 2 files,
> main.c and
> shared.c (shared.c builds into a dll). If I link main.c with the shared
> library then
> when I start debugging main, all breakpoints in shared.c are active.
>
> If I don't link the dll into main but explicitly dlopen it, the
> breakpoints aren't
> active unless I set them after the dlopen.
That sounds like a bug in GDB. We need a test case. Actually, it
sounds like win32/2369. Anyway, there is no reason this should not
work from GDB without your having to do anything special.
> Will this be part of gbd 6.8?
Yes.
> From my point of view, its only fixed when
> I can
> recommend a specific version of Cygwin and/or MinGW to my customers. Even
> then, I'll need to support legacy versions without this feature. So even
> if its
> fixed, I think I'll need to maintain my alternate Windows implementation for
> a while.
If you don't want to ship your own GDB, or require a new release,
then we can't help you with GDB bugs - if you find a time machine
sitting around somewhere, do let me know :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-14 18:14 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
2008-02-14 17:41 ` Gordon Prieur
2008-02-14 18:14 ` Daniel Jacobowitz [this message]
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=20080214181353.GA7518@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