From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Regressions on i686-pc-linux-gnu
Date: Wed, 09 Jan 2008 16:40:00 -0000 [thread overview]
Message-ID: <20080109164017.GA9629@caradoc.them.org> (raw)
In-Reply-To: <4784F826.5060906@de.ibm.com>
On Wed, Jan 09, 2008 at 05:36:54PM +0100, Markus Deuling wrote:
> Why do we have
> http://sourceware.org/ml/gdb-testers/
> and
> http://sourceware.org/ml/gdb-testresults/
> ?
No clue.
>> Did your system C library or compiler change? What does the first new
>> failure look like in gdb.log?
>
> Yes, I switched my distro (glibc 2.5.-18, gcc 4.1.2)
> This one is the first new FAIL:
>
> print str_func1(s)^M
> ^M
> Program received signal SIGTRAP, Trace/breakpoint trap.^M
> str_func1 (s1="test string") at /home/deuling/gdb/dev/gdb/testsuite/gdb.base/call-strs.c:15^M
Looks to me like this is a bunk kernel. I know there was a recent x86
kernel release with this error.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-09 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 15:25 Markus Deuling
2008-01-09 16:28 ` Daniel Jacobowitz
2008-01-09 16:39 ` Markus Deuling
2008-01-09 16:40 ` Daniel Jacobowitz [this message]
2008-01-10 12:58 ` Markus Deuling
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=20080109164017.GA9629@caradoc.them.org \
--to=drow@false.org \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.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