Re: kern/16284 (running function in stoped gdb causes signal 93)

[kamil%NetBSD.org@localhost]

Synopsis: running function in stoped gdb causes signal 93

Responsible-Changed-From-To: kern-bug-people->kamil
Responsible-Changed-By: kamil%NetBSD.org@localhost
Responsible-Changed-When: Sat, 07 Oct 2017 00:01:07 +0200
Responsible-Changed-Why:
Take.

I'm not sure if the original problem is still there, but I'm getting something else:

On Linux:

(gdb) c
Continuing.

^C
Program received signal SIGINT, Interrupt.
0x00007ffff7b1b3d3 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:84
84	in ../sysdeps/unix/syscall-template.S

On NetBSD 8.99.1 amd64 with GDB 7.12

(gdb) r
Starting program: /tmp/bar 
^C
Program received signal SIGINT, Interrupt.
0x00006fe10423b30a in _sys___select50 () from /usr/lib/libc.so.12
(gdb) c
Continuing.
bar: select: Interrupted system call
[Inferior 1 (LWP 0) exited with code 01]
(gdb)

This behavior change is suspicious and I will investigate it in future (but in few days or so).