From: Mark Kettenis <kettenis@wins.uva.nl>
To: guo@cup.hp.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: gdb linux testing regressions (compared to 7/24)
Date: Fri, 11 Aug 2000 11:04:00 -0000 [thread overview]
Message-ID: <200008111804.e7BI4kx09433@delius.kettenis.local> (raw)
In-Reply-To: <Pine.LNX.4.10.10008111010260.30697-100000@hpcll168.cup.hp.com>
Date: Fri, 11 Aug 2000 10:13:08 -0700 (PDT)
From: Jimmy Guo <guo@cup.hp.com>
I'm using redhat 6.1. gcc egcs-2.91.66. How to find out versions for
others like libc? HAVE_PTRACE_GETREGS is defined,
HAVE_PTRACE_GETFPXREGS not.
I probably should have asked for the Linux *kernel* version (uname
-a). If you're running Linux 2.0.x, the failures you're seeing would
be pretty normal.
You can get at the libc version by executing /lib/libc.so.6, but since
you say that HAVE_PTRACE_GETREGS is defined, I'm not really interested
in that information anymore :-).
Mark
next parent reply other threads:[~2000-08-11 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10008111010260.30697-100000@hpcll168.cup.hp.com>
2000-08-11 11:04 ` Mark Kettenis [this message]
2000-08-10 17:56 Jimmy Guo
2000-08-10 18:42 ` Daniel Berlin
2000-08-10 22:02 ` Mark Kettenis
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=200008111804.e7BI4kx09433@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=gdb@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