Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: gdb and Dll
Date: Wed, 27 Nov 2002 16:52:00 -0000	[thread overview]
Message-ID: <20021128005242.GB2696@redhat.com> (raw)
In-Reply-To: <001301c295f5$461850c0$fe78a8c0@SOL>

On Wed, Nov 27, 2002 at 10:13:28AM +0100, Heiko Gerdau wrote:
>Hi,
>
>i found quit a few questions about debugging relocatable dlls on
>Windows, but no answers. Does that mean you can not debug dlls with gdb?

I debug dlls all of the time.

>I found the gdb command "dll-symbols" which seems to be made for this
>purpose. But at least for me, using the mingw version of gdb 5.2.1, it
>seems to have no effects. Is there anybody on this list who could give
>me a hint or confirmation that is it not possible to debug dlls with
>gdb.

AFAIK, the "mingw version" is a modified, unsupported version of gdb.
Certainly simple debugging of dlls with the cygwin version of gdb work
ok, especially in the current cvs revision or, presumably, in the
upcoming gdb 5.3.

There is one long-standing "gotcha" in debugging dlls however.  Currently
you can only set breakpoints on line numbers not on symbol names if the
dll is not loaded.  That is you can't do:

  dll-symbols foo.dll
  bp foo

You have to, instead do:

  dll-symbols foo.dll
  list foo
  bp <first line of foo>

cgf


  parent reply	other threads:[~2002-11-28  0:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-27  1:13 Heiko Gerdau
2002-11-27  8:11 ` Joel Brobecker
2002-11-27 16:52 ` Christopher Faylor [this message]
2002-11-27 16:57   ` Andrew Cagney
2002-11-27 17:11     ` Christopher Faylor
2002-11-27 19:08       ` Christopher Faylor
2002-11-28  4:40         ` Heiko Gerdau
2002-11-28 18:15           ` Christopher Faylor
2002-11-29  4:27             ` Heiko Gerdau
2002-11-28 14:31       ` Andrew Cagney

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=20021128005242.GB2696@redhat.com \
    --to=cgf@redhat.com \
    --cc=gdb@sources.redhat.com \
    /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