From: Andrew Cagney <ac131313@redhat.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb and Dll
Date: Thu, 28 Nov 2002 14:31:00 -0000 [thread overview]
Message-ID: <3DE69930.9080504@redhat.com> (raw)
In-Reply-To: <20021128011154.GE21457@redhat.com>
> FWIW, I mentioned this behavior to a couple of gdb engineers two or
> three years ago and I was almost given to believe that it was expected
> behavior.
Wouldn't suprize me :-(
Users always need to keep GDB developers on their toes by constantly
expanding the bounds of what GDB is expected to do.
Andrew
prev parent reply other threads:[~2002-11-28 22:31 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
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 [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=3DE69930.9080504@redhat.com \
--to=ac131313@redhat.com \
--cc=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