From: Andi Kleen <andi@firstfloor.org>
To: gdb@sourceware.org
Subject: record mode supposed to work on x86_64-linux?
Date: Fri, 15 May 2009 18:41:00 -0000 [thread overview]
Message-ID: <20090515184058.GA7326@basil.nowhere.org> (raw)
Hi,
I was trying the new record/replay mode in CVS. Unfortunately
it doesn't work for me on x86-64-linux. I always get SIGABRTs during
execution. Is this supposed to work already?
Thanks,
-Andi
GNU gdb (GDB) 6.8.50.20090515-cvs
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(gdb) b main
Breakpoint 1 at 0x400544: file tloop2.c, line 5.
(gdb) run
Starting program: /home2/andi/tsrc/tloop2
Breakpoint 1, main () at tloop2.c:5
5 for (i = 0; i < 10; i++)
(gdb) record
(gdb) n
Process record: failed to record execution log.
Program received signal SIGABRT, Aborted.
main () at tloop2.c:5
5 for (i = 0; i < 10; i++)
(gdb)
Process record: failed to record execution log.
Program received signal SIGABRT, Aborted.
main () at tloop2.c:5
5 for (i = 0; i < 10; i++)
(gdb)
--
ak@linux.intel.com -- Speaking for myself only.
next reply other threads:[~2009-05-15 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 18:41 Andi Kleen [this message]
2009-05-16 1:48 ` Hui Zhu
2009-05-16 8:05 ` Andi Kleen
2009-05-16 9:09 ` Hui Zhu
2009-05-16 9:21 ` Andi Kleen
2009-05-16 9:51 ` Hui Zhu
2009-05-16 11:54 ` Andi Kleen
2009-05-16 16:35 ` Pedro Alves
2009-05-17 0:15 ` Hui Zhu
2009-05-17 11:51 ` Pedro Alves
2009-05-17 12:28 ` Hui Zhu
2009-05-17 12:30 ` Pedro Alves
2009-05-17 12:40 ` Hui Zhu
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=20090515184058.GA7326@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=gdb@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