public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug shlibs/11293] New: gdb is broken on Linux/i386 Date: Wed, 17 Feb 2010 19:53:00 -0000 [thread overview] Message-ID: <20100217195339.11293.hjl.tools@gmail.com> (raw) When I ran "make check" on Linux/i386 with gdb trunk on 2010-02-17, I got Starting program: /export/build/gnu/gdb/build-i686-linux/gdb/testsuite/gdb.arch/i386-disp-step ^M /net/gnu-6/export/gnu/import/git/gdb/gdb/solib-svr4.c:1468: internal-error: enable_break: Assertion `load_addr < space_size' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M Quit this debugging session? (y or n) FAIL: gdb.arch/i386-disp-step.exp: running to main in runto (timeout) FAIL: gdb.arch/i386-disp-step.exp: Can't run to main It may be caused by http://sourceware.org/ml/gdb-cvs/2010-02/msg00083.html -- Summary: gdb is broken on Linux/i386 Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: shlibs AssignedTo: unassigned at sourceware dot org ReportedBy: hjl dot tools at gmail dot com CC: gdb-prs at sourceware dot org,jan dot kratochvil at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11293 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-02-17 19:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-17 19:53 hjl dot tools at gmail dot com [this message] 2010-02-17 19:56 ` [Bug shlibs/11293] " hjl dot tools at gmail dot com 2010-02-17 20:02 ` hjl dot tools at gmail dot com 2010-02-17 20:06 ` hjl dot tools at gmail dot com 2010-02-17 20:17 ` hjl dot tools at gmail dot com 2010-02-17 20:47 ` cvs-commit at gcc dot gnu dot org 2010-02-17 20:50 ` hjl dot tools at gmail dot com
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=20100217195339.11293.hjl.tools@gmail.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).