gdb next command seem generate signal 0

Min Wang
Tue Oct 30 22:33:00 GMT 2018


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?



More information about the Gdb mailing list