From: Ian Lance Taylor <ian@airs.com>
To: shebs@cygnus.com, Johanna Svenningsson <mea@nada.kth.se>
Cc: binutils@sourceware.cygnus.com
Subject: Re: [mea@nada.kth.se: AIX 4.3.2 new library and coredump format]
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990518023110.6172.qmail@daffy.airs.com> (raw)
In-Reply-To: <199905170420.VAA14135@andros.cygnus.com>
Date: Sun, 16 May 1999 21:20:17 -0700
From: Stan Shebs <shebs@cygnus.com>
Here is a set of BFD patches that are a start on supporting AIX 4.3 in
GDB. Could someone please evaluate these and install if they're OK?
The theory seems plausible, although upon reading these I realize that
my BFD-remembering neurons must be dying off...
To: gdb-patches@cygnus.com
Subject: AIX 4.3.2 new library and coredump format
From: Johanna Svenningsson <mea@nada.kth.se>
Date: 27 Mar 1999 06:14:58 +0200
Thanks for sending the patches. The look basically OK, but still need
some work.
I didn't look at every line, but:
* The formatting does not follow the GNU standard, and must be fixed.
* I don't understand the new code in rs6000coff_core_p. It appears to
only read the new format if it can not read sizeof (struct
core_dump) bytes from the file. That seems unlikely, so I don't
understand how this code could work at all.
* The archive code appears to have been modified to always generate
big archive files, which will presumably break the native tools on
older versions of AIX. This needs to be fixed.
I believe these patches are large enough to require a gdb or binutils
copyright assignment.
Ian
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Stan Shebs
1999-07-01 0:00 ` Ian Lance Taylor [this message]
1999-07-01 0:00 ` Johanna Svenningsson
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=19990518023110.6172.qmail@daffy.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.cygnus.com \
--cc=mea@nada.kth.se \
--cc=shebs@cygnus.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).