Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
Cc: tromey@cygnus.com (Tom Tromey), guo@cup.hp.com (Jimmy Guo),
	gdb-patches@sourceware.cygnus.com
Subject: Re: Patch: gdb -vs- Debian 2.0
Date: Fri, 19 Nov 1999 10:57:00 -0000	[thread overview]
Message-ID: <199911191857.KAA20019@ferrule.cygnus.com> (raw)
In-Reply-To: <19991119185237.A1A271B493@ocean.lucon.org>

>>>>> "HJ" == H J Lu <hjl@lucon.org> writes:

HJ> FWIW, the single binary of my gdb 4.17.0.14 works with all Linux
HJ> kernels. It detects everything at runtime.

That is what my patch does too.
Can you say why one might be better or worse?  I haven't seen your
change here.

Tom
From tromey@cygnus.com Fri Nov 19 10:58:00 1999
From: Tom Tromey <tromey@cygnus.com>
To: Jimmy Guo <guo@cup.hp.com>
Cc: Tom Tromey <tromey@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: Patch: gdb -vs- Debian 2.0
Date: Fri, 19 Nov 1999 10:58:00 -0000
Message-id: <199911191858.KAA20022@ferrule.cygnus.com>
References: <199911191800.KAA19976@ferrule.cygnus.com> <Pine.LNX.4.10.9911191052490.4001-100000@hpcll168.cup.hp.com>
X-SW-Source: 1999-q4/msg00302.html
Content-length: 226

>>>>> "Jimmy" == Jimmy Guo <guo@cup.hp.com> writes:

Jimmy> Just tried a build on the Redhat 5.1 system ... yes,
Jimmy> PTRACE_(GET|SET)[FP]REGS were not defined.

My patch doesn't fix this, but it would be easy to fix.

T




      parent reply	other threads:[~1999-11-19 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8766yzgg67.fsf@cygnus.com>
     [not found] ` <Pine.LNX.4.10.9911190919190.4001-100000@hpcll168.cup.hp.com>
1999-11-19 10:00   ` Tom Tromey
     [not found]     ` <19991119185237.A1A271B493@ocean.lucon.org>
1999-11-19 10:57       ` Tom Tromey [this message]

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=199911191857.KAA20019@ferrule.cygnus.com \
    --to=tromey@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=guo@cup.hp.com \
    --cc=hjl@lucon.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