#780690 [gdb] Attempting to record kvirc results in failure to cope with 'syscall number -1'

Package:
gdb
Source:
gdb
Description:
GNU Debugger
Submitter:
OmegaPhil
Date:
2015-08-29 15:42:03 UTC
Severity:
normal
#780690#5
Date:
2015-03-17 20:35:12 UTC
From:
To:
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
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
#780690#10
Date:
2015-08-28 16:46:04 UTC
From:
To:
Could you please re-try with version in unstable, 7.9.1-1? And try to discuss with upstream in case the feature is still broken.

Regards
#780690#15
Date:
2015-08-29 15:30:14 UTC
From:
To:
I've just tested with v7.9.1 with galculator, same outcome:

====================================================================

(gdb) start
Temporary breakpoint 1 at 0x40a830
Starting program: /usr/bin/galculator
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Temporary breakpoint 1, 0x000000000040a830 in main ()
(gdb) record
(gdb) continue
Continuing.
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
(null)Process record: failed to record execution log.

[Thread 0x7ffff7f97980 (LWP 1778)] #1 stopped.
0x00007ffff6326e7e in __recvmsg_nocancel () at
../sysdeps/unix/syscall-template.S:81
81	../sysdeps/unix/syscall-template.S: No such file or directory.

====================================================================

I've had a look at their bug tracker, there are 566 open bugs currently
(...) with a few mentioning record, even one where I posted over a year
ago to, completely ignored:

https://sourceware.org/bugzilla/show_bug.cgi?id=16785#c1

So it seems to be unmaintained (according to my definition) - not going
to waste my time posting a further bug (being ignored just makes me very
angry, and I not programming to be angry).