From: Pierre Muller <muller@ics.u-strasbg.fr>
To: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA-v3] win32-nat.c: Add dll names if debugevents is on
Date: Wed, 18 Jun 2008 01:43:00 -0000 [thread overview]
Message-ID: <20080618001933.tgxx233giok4gk4g@webmail.u-strasbg.fr> (raw)
In-Reply-To: <20080617042351.GA13112@ednor.casa.cgf.cx>
Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> a écrit :
> On Mon, Jun 16, 2008 at 04:32:06AM +0100, Pedro Alves wrote:
>> 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. ;-)
>
> Ok. This is the kind of response I was looking for.
>
> I'd like to have as little special case stuff in gdb as possible. We
> have been moving in that direction and that's good.
>
> "set debugevents" is a special case behavior for Windows gdb. I didn't
> add it and I've wondered why it was necessary in the first place since I
> don't recall ever feeling its lack on linux.
>
> However, I guess I'll approve the patch since I can see why it would be
> useful to have this information and it doesn't seem like there is
> anything else that could be pressed into service in gdb-proper.
Christopher,
you didn't reply to my answer to your first email in that thread,
http://sourceware.org/ml/gdb-patches/2008-06/msg00306.html
and I am quite confused by your wording?
Should I understand this as an approval?
Or is it just because you did not see my reply?
In that case, is it because I did not send to you?
I always suppress your email from the recipients
because of the use-the-mailinglist suffix, but maybe you only mean
that we should never reply only personnally to you?
Pierre Muller
GDB pascal language maintainer
next prev parent reply other threads:[~2008-06-17 22:20 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
2008-06-17 9:51 ` Christopher Faylor
2008-06-17 18:21 ` Christopher Faylor
2008-06-18 1:43 ` Pierre Muller [this message]
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=20080618001933.tgxx233giok4gk4g@webmail.u-strasbg.fr \
--to=muller@ics.u-strasbg.fr \
--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