Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Lamy-Charrier <david.lamy@gmail.com>
To: gdb@sourceware.org
Subject: Re: regression: support for spaces in dll path on Windows
Date: Thu, 08 Dec 2005 18:26:00 -0000	[thread overview]
Message-ID: <6541ed4c0512081025u42cf899p2d67e5efadde6d1a@mail.gmail.com> (raw)
In-Reply-To: <20051207191923.GB19243@trixie.casa.cgf.cx>

Hi,

I get a release ported to MinGw from MinGw Website, for GDB it is the
CVS Head on November 16, 2005.

Finally, after investigating the problem, it looks like a problem in
win32-nat.c:
in register_loaded_dll(), the field so->so_name is not initialized
before calling solib_symbols_add() function. So this function
solib_symbols_add()  returns immediately.

I don't know if this has been fixed already.

David


On 12/7/05, Christopher Faylor
<cgf-use-the-mailinglist-please@sourceware.org> wrote:
> On Wed, Dec 07, 2005 at 02:33:35PM +0100, David Lamy-Charrier wrote:
> >I am trying to debug a .exe that loads a .dll on a WinXp Pro PC with a
> >MinGW gdb version taken from CVS head on November 16.
> >When my .exe loads a dll, gdb gets the LOAD_DLL_DEBUG_EVENT but it
> >fails to load the debug info of the dll because there are some spaces
> >in the path to my dll.
> >
> >I tried with a GDB 6.3_1 MinGW and it works well with blank in path
> >names, but I have a problem when it tries to decode the stack frame
> >(certainly because the .exe has been compiled by Microsoft VC6.0 in
> >release mode).
> >
> >Does anyone know where I should look in the source code to:
> >- patch the stack frame decoding problem on gdb 6.3_1
> >or
> >- patch the space in path names to dll problem on latest version of gdb ??
>
> What version of gdb are you running which displays the problem and
> where did you get it?
>
> cgf
>


      reply	other threads:[~2005-12-08 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 13:33 David Lamy-Charrier
2005-12-07 19:19 ` Christopher Faylor
2005-12-08 18:26   ` David Lamy-Charrier [this message]

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=6541ed4c0512081025u42cf899p2d67e5efadde6d1a@mail.gmail.com \
    --to=david.lamy@gmail.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