This is the mail archive of the gdb@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]

gdb next command seem generate signal 0

From: Min Wang <mwang at lifesize dot com>
To: "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Tue, 30 Oct 2018 22:33:33 +0000
Subject: gdb next command seem generate signal 0

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

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