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 record/28461] New: [m32] FAIL: gdb.reverse/fstatat-reverse.exp: continue to breakpoint: marker2
Date: Sat, 16 Oct 2021 20:42:28 +0000 [thread overview]
Message-ID: <bug-28461-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28461
Bug ID: 28461
Summary: [m32] FAIL: gdb.reverse/fstatat-reverse.exp: continue
to breakpoint: marker2
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: record
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On openSUSE Tumbleweed with target board unix/-m32 I run into:
...
(gdb) PASS: gdb.reverse/fstatat-reverse.exp: set breakpoint at marker2
continue^M
Continuing.^M
Process record and replay target doesn't support syscall number 383^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0xf7fc9545 in __kernel_vsyscall ()^M
(gdb) FAIL: gdb.reverse/fstatat-reverse.exp: continue to breakpoint: marker2
...
GDB configured as:
...
$ gdb -configuration
This GDB was configured as follows:
configure --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-auto-load-dir=$debugdir:$datadir/auto-load
--with-auto-load-safe-path=$debugdir:$datadir/auto-load
--with-expat
--with-gdb-datadir=/data/gdb_versions/devel/install/share/gdb
(relocatable)
--with-jit-reader-dir=/data/gdb_versions/devel/install/lib64/gdb
(relocatable)
--without-libunwind-ia64
--without-lzma
--with-babeltrace
--without-intel-pt
--with-mpfr
--without-xxhash
--with-python=/usr
--with-python-libdir=/usr/lib
--with-debuginfod
--with-guile
--disable-source-highlight
--with-separate-debug-dir=/usr/lib/debug
--with-system-gdbinit=/data/gdb_versions/devel/system-gdbinit
("Relocatable" means the directory can be moved with the GDB installation
tree, and GDB will still find it.)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-16 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 20:42 vries at gcc dot gnu.org [this message]
2022-05-06 15:01 ` [Bug record/28461] " vries at gcc dot gnu.org
2022-05-06 15:01 ` vries at gcc dot gnu.org
2022-05-09 10:42 ` vries at gcc dot gnu.org
2022-06-07 14:43 ` 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-28461-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).