From: Andrew Cagney <cagney@gnu.org>
To: Roland McGrath <roland@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] auxv support
Date: Wed, 25 Feb 2004 03:59:00 -0000 [thread overview]
Message-ID: <403C1D90.5080106@gnu.org> (raw)
In-Reply-To: <200402240350.i1O3oIFk027102@magilla.sf.frob.com>
> I've written a new test case for the live process support, grokking native
> core files, and gcore. It works peachy on Linux 2.6 and on Solaris. It
> should work omitting the native core dump part for remote, but I don't know
> off hand how to test that. Are there runtest arguments to make it run
> gdbserver for tests? (I tried --target_board linux-gdbserver, but that
> tries to do "rsh linux-gdbserver ../gdbserver/gdbserver ..." instead of
> running gdbserver locally. I can't figure out how to make it not use rsh,
> or use a hostname other than "linux-gdbserver".)
I'd not worry (I think that should instead use "(gdb) target remote
|gdbserver").
> However, on a system that does not support getting the auxv data, it shows
> three failures. What is the right thing to do about this? The difficulty
> is that the error from `info auxv' does not distinguish an error/bug in
> reading the data from the target code not supporting auxv access or from
> the native system not supporting the access even though the gdb target code
> does (e.g. Linux < 2.6).
Just a few tweaks:
> 2004-02-23 Roland McGrath <roland@redhat.com>
>
> * gdb.base/auxv.exp: New file.
>
> Index: testsuite/gdb.base/auxv.exp
> ===================================================================
> RCS file: testsuite/gdb.base/auxv.exp
> diff -N testsuite/gdb.base/auxv.exp
> --- /dev/null 1 Jan 1970 00:00:00 -0000
> +++ testsuite/gdb.base/auxv.exp 24 Feb 2004 03:06:02 -0000
> @@ -0,0 +1,186 @@
> +# Test `info auxv' and related functionality.
> +
> +# Copyright 1992,93,94,95,96,97,98,99,2000,04 Free Software Foundation, Inc.
Just write the years in full.
> +set testfile "coremaker2"
> +set srcfile ${testfile}.c
Here a new file "auxv.c" is prefered for the new test (making a copy of
coremaker2.c is ok).
Otherwize, remember to post the final patch when committing,
thanks,
Andrew
> +set binfile ${objdir}/${subdir}/${testfile}
> +set corefile ${objdir}/${subdir}/${testfile}.corefile
> +set gcorefile ${objdir}/${subdir}/${testfile}.gcore
next prev parent reply other threads:[~2004-02-25 3:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 2:59 Roland McGrath
2004-01-29 6:39 ` Eli Zaretskii
2004-01-29 8:20 ` Roland McGrath
2004-01-29 20:14 ` Eli Zaretskii
2004-01-29 21:31 ` Roland McGrath
2004-01-30 19:03 ` Daniel Jacobowitz
2004-01-30 23:35 ` Andrew Cagney
2004-01-30 23:51 ` Roland McGrath
2004-01-31 0:11 ` Andrew Cagney
2004-01-31 0:16 ` Roland McGrath
2004-02-02 14:27 ` Andrew Cagney
2004-02-17 16:35 ` Andrew Cagney
2004-02-18 2:08 ` Roland McGrath
2004-02-24 3:50 ` Roland McGrath
2004-02-25 3:59 ` Andrew Cagney [this message]
2004-03-19 0:09 ` [COMMITTED PATCH] testsuite for info auxv Roland McGrath
2004-03-17 20:46 ` Roland McGrath
2004-02-25 4:03 ` [PATCH] auxv support Daniel Jacobowitz
2004-02-25 20:38 ` Roland McGrath
[not found] <200401310013.i0V0DnGE018646@magilla.sf.frob.com>
2004-02-01 6:04 ` Daniel Jacobowitz
2004-02-01 22:36 ` Roland McGrath
2004-02-02 0:11 ` Roland McGrath
2004-02-02 6:24 ` Eli Zaretskii
2004-02-02 14:17 ` Andrew Cagney
2004-02-02 14:25 ` Andrew Cagney
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=403C1D90.5080106@gnu.org \
--to=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=roland@redhat.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