This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug cli/19528] New: "handle" is too picky about numbers
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 28 Jan 2016 22:52:56 +0000
- Subject: [Bug cli/19528] New: "handle" is too picky about numbers
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19528
Bug ID: 19528
Summary: "handle" is too picky about numbers
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
Target Milestone: ---
My inferior stopped in a signal handler, something I wasn't expecting.
It's a "normal" signal so I wanted to just ignore it on the gdb
side and keep going.
When stopping I saw:
JitInterruptHandler (signum=26, info=0x7ffffc766070, context=0x7ffffc765f40) at
/home/tromey/firefox-git/hg2/js/src/asmjs/WasmSignalHandlers.cpp:1215
So I tried:
(gdb) handle 26 nostop noprint pass
Only signals 1-15 are valid as numeric signals.
Use "info signals" for a list of symbolic signals.
I think this is overly picky.
I know the signal number but finding the name is a bit of a pain.
gdb should accept numbers everywhere.
Relatedly, it would be nice if gdb could display its name/number mapping.
--
You are receiving this mail because:
You are on the CC list for the bug.