From: Paul Koning <pkoning@equallogic.com>
To: sawitt@electra.rsc.raytheon.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB can't read core
Date: Wed, 26 Nov 2003 22:22:00 -0000 [thread overview]
Message-ID: <16325.10163.916133.242883@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.56.0311261310460.21580@zeus.rsc.raytheon.com>
Last I looked at this (in 5.3) there was a general presumption in gdb
that it would never support core dump reading in any cross-gdb.
I beat on it for a while to get rid of that assumption; it was not
totally trivial but not all that hard, either. But it was a bit of a
hack job, so I'm not prepared to submit the resulting changes as gdb
patches.
Is this considered the Right Way for it to behave? Or is this a
deficiency that's awaiting fixing in some grand overhaul?
paul
next prev parent reply other threads:[~2003-11-26 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 21:27 Stephen A. Witt
2003-11-26 22:22 ` Paul Koning [this message]
2003-11-26 22:29 ` Daniel Jacobowitz
2003-11-26 22:34 ` Paul Koning
2003-11-26 22:37 ` Daniel Jacobowitz
2003-12-01 16:05 ` 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=16325.10163.916133.242883@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=gdb@sources.redhat.com \
--cc=sawitt@electra.rsc.raytheon.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