From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Racy FAIL: gdb.base/auxv.exp + gdb.base/callfuncs.exp [Re: [patch/rfc] Recognize non-DW_AT_location <value optimized out> symbols]
Date: Fri, 20 Mar 2009 19:54:00 -0000 [thread overview]
Message-ID: <20090320191841.GE12530@adacore.com> (raw)
In-Reply-To: <20090320183838.GA8318@host0.dyn.jankratochvil.net>
> gdb/testsuite/
> 2009-03-20 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Fix a racy FAIL.
> * gdb.base/auxv.exp (fetch_auxv): Fix trailing newlines consumption.
> * gdb.base/callfuncs.exp (fetch_all_registers): Likewise.
This looks OK to me.
But I have a question: Does anyone know who is responsible for us
getting CR/LF as line-endings even on Unix? Is that expect? dejagnu?
our gdb-testsuite framework? I can't find any information on the web
nor find a clue in gdb/testsuite/lib :-(.
--
Joel
next prev parent reply other threads:[~2009-03-20 19:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 21:15 [patch/rfc] Recognize non-DW_AT_location <value optimized out> symbols Jan Kratochvil
2009-03-20 15:17 ` Joel Brobecker
2009-03-20 15:51 ` Joel Brobecker
2009-03-20 18:22 ` Jan Kratochvil
2009-03-20 18:39 ` Joel Brobecker
2009-03-20 18:51 ` [patch] Racy FAIL: gdb.base/auxv.exp + gdb.base/callfuncs.exp [Re: [patch/rfc] Recognize non-DW_AT_location <value optimized out> symbols] Jan Kratochvil
2009-03-20 19:54 ` Joel Brobecker [this message]
2009-03-20 21:54 ` Daniel Jacobowitz
2009-03-23 17:36 ` Joel Brobecker
2009-03-23 17:45 ` Jan Kratochvil
2009-03-23 22:52 ` Joel Brobecker
2009-03-24 23:50 ` [patch/rfc] Recognize non-DW_AT_location <value optimized out> symbols [Re: [patch] Racy FAIL: gdb.base/auxv.exp + gdb.base/callfuncs.exp] Jan Kratochvil
2009-03-25 10:03 ` [patch/rfc] Recognize non-DW_AT_location <value optimized out> symbols Jan Kratochvil
2009-03-26 0:38 ` Joel Brobecker
2009-03-26 17:02 ` Jan Kratochvil
2009-03-20 19:18 ` Joel Brobecker
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=20090320191841.GE12530@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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