public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* gdb next command seem generate signal 0
@ 2018-10-30 22:33 Min Wang
  0 siblings, 0 replies; only message in thread
From: Min Wang @ 2018-10-30 22:33 UTC (permalink / raw)
  To: gdb

Hi


I am using  gdb: 8.2-0ubuntu1~16.04.1 inside a container which was hosted on a debian 9 with Docker version 18.06.1-ce, build e68fc7a.


We have a program which catch some linux signal.


I set a breakpoint somewhere, the gdb can hit that breakpoint,


every time  I ran next command, I got signal 0 passed to our program.


Is it a bug in gdb? It seems there is no way to  catch signal 0 in gdb.


If not, could some one explain it? why the signal 0?




thanks



min




^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2018-10-30 22:33 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-30 22:33 gdb next command seem generate signal 0 Min Wang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).