From: Nick Clifton <nickc@cambridge.redhat.com>
To: Greg Lehey <grog@lemis.com>
Cc: Aaron Schlesinger <mortehl@yahoo.com>, binutils@sources.redhat.com
Subject: Re: Binutils 2.11 and BSDI 4.2 - **BUG**
Date: Wed, 15 Aug 2001 01:16:00 -0000 [thread overview]
Message-ID: <m3n151211m.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <20010815114918.H49989@wantadilla.lemis.com>
Hi Greg,
> Maybe I'm missing something here, but BSD/OS has always supported
> core dumping. Are you talking about something else?
He is talking about something else - it is the binutils ability to
display the contents of core files that is at stakes here. In
particular with this patch applied it means that objdump will not be
able to display the contents of a core file created on an x86 BSDI
system. It will not stop the system from creating them, and debug
tools should still be able to process them, it is just that objdump
will not be able to disassemble them.
Of course if you can work out what is different about core files on
BSDI systems (as opposed to say, netBSD systems), it should be
possible to add support for that format to the BFD library and then
restore binutils' support for core files on BSDI.
Cheers
Nick
next prev parent reply other threads:[~2001-08-15 1:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 19:58 Binutils 2.11 and BSDI 4.2 Aaron Schlesinger
2001-08-12 2:06 ` Nick Clifton
2001-08-14 6:53 ` Aaron Schlesinger
2001-08-14 7:16 ` Nick Clifton
2001-08-14 19:10 ` Binutils 2.11 and BSDI 4.2 - **BUG** Aaron Schlesinger
2001-08-14 19:19 ` Greg Lehey
2001-08-14 19:33 ` Aaron Schlesinger
2001-08-14 19:45 ` Greg Lehey
2001-08-15 1:16 ` Nick Clifton [this message]
2001-08-23 7:34 ` Binutils 2.11 and BSDI 4.2 Nick Clifton
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=m3n151211m.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=binutils@sources.redhat.com \
--cc=grog@lemis.com \
--cc=mortehl@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).