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:00:00 -0000 [thread overview]
Message-ID: <199911191800.KAA19976@ferrule.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9911190919190.4001-100000@hpcll168.cup.hp.com>
Jimmy> One more bit of information -- gdb used to compile on Linux
Jimmy> Redhat 5.1 (the PC cannot be upgraded to more recent versions
Jimmy> due to onboard SCSI controller <-> Linux driver problem), but
Jimmy> some time ago quite recently I have to compile gdb on Linux
Jimmy> Redhat 6.0, probably due to the same change Tom's patch is
Jimmy> trying to fix.
Was the problem that PTRACE_GETREGS was not defined? If so, then that
is a slightly different problem, with a slightly different fix.
PTRACE_GETREGS is defined on my machine, it just doesn't work.
Tom
next parent reply other threads:[~1999-11-19 10:00 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 [this message]
[not found] ` <19991119185237.A1A271B493@ocean.lucon.org>
1999-11-19 10:57 ` Tom Tromey
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=199911191800.KAA19976@ferrule.cygnus.com \
--to=tromey@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=guo@cup.hp.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