From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] preliminary support for hppa-linux
Date: Sun, 04 Apr 2004 16:21:00 -0000 [thread overview]
Message-ID: <20040404162144.GA27320@nevyn.them.org> (raw)
In-Reply-To: <20040404064432.GM750@tausq.org>
On Sat, Apr 03, 2004 at 10:44:32PM -0800, Randolph Chung wrote:
> Hi, this is part 1 of my attempt to get gdb support for hppa-linux
> upstream. There have been several failed attempts in the past... let's
> see if we can fix it for real this time :)
>
> Attached is a "minimal" patch to get gdb building on hppa-linux and have
> some basic functionality. There are still many bugs which we will try to
> fix in subsequent patches. The bulk of this patch moves some
> hpux-specific code from hppa-tdep.c into hppa-hpux-tdep.c. This allows
> hppa-linux to share most of the code in hppa-tdep.c.
>
> This patch contains a bit of code that has been floating around in
> Debian for a number of years. As far as I know, it was mostly
> contributed by Alan Modra and David Huggin-Daines as part of LinuxCare's
> contract with HP for the initial hppa-linux work. In any case, there
> have been many changes to gdb since then and the patch has been changed
> many times by various people. As far as I know all the contributors have
> copyright assignment with the FSF.
>
> Tested on hppa2.0w-hp-hpux11.11 (with gcc) and hppa-unknown-linux-gnu.
> Comments appreciated.
This is too all-over-the-place. This code has hung around for a number
of years now, and GDB's kept moving - so each bit of this needs to be
reviewed as we go along to make sure we don't re-add unnecessary
garbage. For instance, GDB_TARGET_IS_PA_ELF is unused now, so there's
no content in tm-linux.h.
You also moved a lot of code out of hppa-tdep.c without ever adding
hppa-hpux-tdep.c to the HP/UX target - oops.
Let's do one thing at a time. Could you submit a patch which just
moves the HP/UX code out of hppa-tdep.c, with the above problem fixed?
Preferably without changing any of it.
> 2004-04-03 Randolph Chung <tausq@debian.org>
>
> * hppa-tdep.c: (args_for_find_stub): Move to hppa-hpux-tdep.c
> (hp_som_som_object_present): Likewise.
> (exception_catchpoints_are_fragile): Likewise.
You can say:
* hppa-tdep.c (args_for_find_stub, hp_som_som_object_present)
(exception_catchpoints_are_fragile, find_stub_with_shl_get)
[et cetera]
(setup_d_pid_in_inferior): Move to hppa-hpux-tdep.c.
* hppa-hpux-tdep.c: New file.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-04-04 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 4:57 Randolph Chung
2004-04-04 6:01 ` Eli Zaretskii
2004-04-04 6:29 ` Randolph Chung
2004-04-04 7:12 ` Eli Zaretskii
2004-04-04 16:21 ` Daniel Jacobowitz [this message]
2004-04-04 16:28 ` Daniel Jacobowitz
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=20040404162144.GA27320@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.org \
/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