From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
Subject: Re: [RFA-v3] win32-nat.c: Add dll names if debugevents is on
Date: Mon, 16 Jun 2008 06:38:00 -0000 [thread overview]
Message-ID: <200806160432.06714.pedro@codesourcery.com> (raw)
In-Reply-To: <20080615225330.GA7678@ednor.casa.cgf.cx>
A Sunday 15 June 2008 23:53:30, Christopher Faylor wrote:
> I guess my basic question here is why is this needed at all? Does
> the non-windows version of gdb have something similar? If so, this
> should be patterned after that. If not, why is Windows special?
Well, with set "set verbose 1" you can see dll names being
read in already, but you also get a lot more. This is just a
couple of lines to add some debug output. Note that it
can't be much patterned (without some extra hair) other than
printing the so name, because the solib.c doesn't know a
thing about each solib's struct lm_info implementation. Then
again, I only suggested to add the image base to the output
because it was handy... Anyway, I've already spent more time
in this thread than it takes to add debug output locally
every time I'd need it. It's in Pierre's court to argue. ;-)
--
Pedro Alves
next prev parent reply other threads:[~2008-06-16 3:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 15:28 [RFA] " Pierre Muller
2008-06-13 15:35 ` Pedro Alves
2008-06-13 23:07 ` Pierre Muller
2008-06-14 0:16 ` Pedro Alves
2008-06-14 3:20 ` [RFA-v3] " Pierre Muller
2008-06-16 1:26 ` Christopher Faylor
2008-06-16 6:38 ` Pedro Alves [this message]
2008-06-17 9:51 ` Christopher Faylor
2008-06-17 18:21 ` Christopher Faylor
2008-06-18 1:43 ` Pierre Muller
2008-06-18 7:33 ` Christopher Faylor
2008-06-18 13:40 ` Pierre Muller
2008-06-16 11:43 ` Pierre Muller
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=200806160432.06714.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=cgf-use-the-mailinglist-please@sourceware.org \
--cc=gdb-patches@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