Package: gdb Version: 7.7.1+dfsg-5 Severity: normal I'd like to test out gdb's recording functionality on the KVIrc SVN source (svn co https://svn.kvirc.de/svn/trunk/kvirc), however shortly after starting up gdb -> record -> continue, I get the following message:
==================================================================
Process record and replay target doesn't support syscall number -1
Process record: failed to record execution log.
==================================================================
I then did this with a simpler program, galculator straight from the
Debian repo, and this was even more useless:
==================================================================
Do you want to auto delete previous execution log entries when
record/replay buffer becomes full (record full stop-at-limit)?([y] or n) y
Process record: failed to record execution log.
==================================================================
is the record functionality considered too buggy to use currently? I've
only tried occassionally, never seeing it work.
Thanks
--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64
Debian Release: 8.0
990 testing 10.1.0.3
500 unstable 10.1.0.3
500 quodlibet-unstable 10.1.0.3
1 experimental 10.1.0.3
--- Package information. ---
Depends (Version) | Installed
=========================================-+-=========================
libc6 (>= 2.15) |
libexpat1 (>= 2.0.1) |
liblzma5 (>= 5.1.1alpha+20110809) |
libncurses5 (>= 5.5-5~) |
libpython2.7 (>= 2.7) |
libreadline6 (>= 6.0) |
libtinfo5 |
zlib1g (>= 1:1.2.0) |
Recommends (Version) | Installed
=========================-+-===========
libc-dbg |
gdbserver | 7.7.1+dfsg-5
Suggests (Version) | Installed
=======================-+-===========
gdb-doc | 7.7.1+dfsg-2
signature.asc
Description: OpenPGP digital signature
