From: Christopher Faylor <cgf@redhat.com>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 5.3 Branch 4th Sept 00:00 GMT
Date: Thu, 29 Aug 2002 15:16:00 -0000 [thread overview]
Message-ID: <20020829221635.GF23580@redhat.com> (raw)
In-Reply-To: <200208292108.g7TL8ep10818@hyper.wm.sps.mot.com>
On Thu, Aug 29, 2002 at 05:08:40PM -0400, Peter Barada wrote:
>
>>Personally, I'd consider the bug that I posted earlier today to be a
>>show stopper since it has the possibility of causing a SEGV from doing
>>a simple gdb operation. Or, maybe I'm the only person around who does
>>a "display /i $pc"...
>
>I seriously doubt that. I use disp/i $pc all the time (its especially
>helpful for debugging Linux kernel TLB miss code, or figuring out
>where my experimental ColdFire compiler generates incorrect code).
Feel free to doubt it, especially without reading the bug report.
cgf
next prev parent reply other threads:[~2002-08-29 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 8:37 Andrew Cagney
2002-08-29 8:48 ` Daniel Jacobowitz
2002-08-29 14:00 ` Christopher Faylor
2002-08-29 14:08 ` Peter Barada
2002-08-29 15:16 ` Christopher Faylor [this message]
2002-08-29 17:15 ` Christopher Faylor
2002-09-05 12:45 ` 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=20020829221635.GF23580@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=pbarada@mail.wm.sps.mot.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