public inbox for
 help / color / mirror / Atom feed
From: FengLingDu <>
To: "" <>
Subject: Program received signal SIGTRAP, Trace/breakpoint trap
Date: Sat, 16 Apr 2022 21:54:29 +0800 (GMT+08:00)	[thread overview]
Message-ID: <> (raw)

Hello gdb:

First for english is not my native language, please excuse typing errors.
I have google a bit and found some clues on stackoveflow, but it seems useless to me.

I expect to find out how the singal works which depends on the PCNTL module,  
so I decided to debug PHP-CLI binary with a demo php script with gdb,  
and the debug environment is listed as below:

1. get php-cli binary by compiling from source with GCC 4.4.7
2. php version: 7.0.2
3. gdb version: 7.2-60.el6_4.1
4. system platform: CentOS 6.5

My trouble is:
it seems to be ok when I debug step-by-step forward,  
but it will always throw the message like below after I send a kill -10 pid or else:
"Program received signal SIGTRAP, Trace/breakpoint trap.",
then I issue continuously the "finish" command attempting to jump out of the current function,  
but it failed unless many many times command execution for "finish",  
but event so,  it still reports the message metioned above again and again.

So what happened here and what does the meaning of the SIGTRAP ?
Need something else to provide? please tell me, thanks a lot.

Best regards, FengLingDu.

             reply	other threads:[~2022-04-16 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 13:54 FengLingDu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-24  3:13 John Smith
2012-07-24 17:05 ` Pedro Alves
2005-09-19 16:57 Ajay Patel
2005-09-20  5:08 ` divick kishore
2005-09-19  7:05 divick kishore
2005-09-19  7:56 ` Ramana Radhakrishnan
2005-09-19 10:09   ` divick kishore
2003-05-15 18:44 Smita
2003-05-15 19:21 ` Tim Combs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).