* Is it possible to make gdb stop on actual failure, and not inside of signal or inside of assert function?
@ 2021-11-05 17:21 Yuri
0 siblings, 0 replies; only message in thread
From: Yuri @ 2021-11-05 17:21 UTC (permalink / raw)
To: gdb
I start gdb from the signal handler of the debugged process.
When SEGV happens the signal handler starts 'gdb -p $PPID' using the
'system' function.
gdb stops inside of the signal handler, inside of the system call, in
_wait4().
This is 7 levels below the SEGV location.
Is there a way to make gdb skip signal handler and stop at the actual
problem location,
which is the line that caused SEGV in my case?
gdb-11.1
FreeBSD 13
Thank you,
Yuri
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-11-05 17:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-05 17:21 Is it possible to make gdb stop on actual failure, and not inside of signal or inside of assert function? Yuri
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).