This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug cli/17300] crash in non-stop mode with continue -a & (readline_callback_read_char() called with no handler!)


https://sourceware.org/bugzilla/show_bug.cgi?id=17300

--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
It seems GDB loses the & in "c -a&" when putting that command in the history (a
bug in itself), and so the second <RET> actually executes "c -a".  Here's what
I've reduced the reproducer to so far:

$ gdb -ex "set non-stop on" --args /usr/bin/sleep 10000
(gdb) r
Starting program: /usr/bin/sleep 10000
^C
Program received signal SIGINT, Interrupt.
0x00000033356bc780 in __nanosleep_nocancel () at
../sysdeps/unix/syscall-template.S:81
81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
(gdb) c -a&
Continuing.
(gdb) c -a
Continuing.

readline: readline_callback_read_char() called with no handler!

Program received signal SIGABRT, Aborted.
0x0000003335635887 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(top-gdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]