public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/27205] New: [-m32] FAIL: gdb.base/longjmp.exp: next over longjmp(1)
Date: Tue, 19 Jan 2021 15:51:25 +0000 [thread overview]
Message-ID: <bug-27205-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27205
Bug ID: 27205
Summary: [-m32] FAIL: gdb.base/longjmp.exp: next over
longjmp(1)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On openSUSE Factory I see with target board unix/-m32:
...
(gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1)
next^M
Warning:^M
Cannot insert breakpoint 0.^M
Cannot access memory at address 0xcfb589ee^M
^M
__libc_siglongjmp (env=0x804c040 <env>, val=1) at ../setjmp/longjmp.c:30^M
30 }^M
(gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-19 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 15:51 vries at gcc dot gnu.org [this message]
2021-01-23 6:38 ` [Bug breakpoints/27205] " vries at gcc dot gnu.org
2021-01-23 9:02 ` vries at gcc dot gnu.org
2021-01-23 9:30 ` vries at gcc dot gnu.org
2021-01-23 9:50 ` vries at gcc dot gnu.org
2021-01-27 14:31 ` vries at gcc dot gnu.org
2021-01-28 9:59 ` cvs-commit at gcc dot gnu.org
2021-01-28 10:02 ` vries at gcc dot gnu.org
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=bug-27205-4717@http.sourceware.org/bugzilla/ \
--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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).