public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* Program received signal SIGTRAP, Trace/breakpoint trap
@ 2005-09-19  7:05 divick kishore
  2005-09-19  7:56 ` Ramana Radhakrishnan
  0 siblings, 1 reply; 10+ messages in thread
From: divick kishore @ 2005-09-19  7:05 UTC (permalink / raw)
  To: gdb

Hi,
   I am getting the above error when I am trying to
debug a 64 but application. I have no clue why it
happens. The exact message from gdb is as below. Any
suggestions?


Program received signal SIGTRAP, Trace/breakpoint
trap.
[Switching to Thread 2305843009239495296 (LWP 29455)]
<signal handler called>
(gdb) bt
#0  <signal handler called>
Cannot access memory at address 0xfb0000000000528


Thanks,
Divick



		
__________________________________________________________ 
Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.com

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Program received signal SIGTRAP, Trace/breakpoint trap
@ 2022-04-16 13:54 FengLingDu
  0 siblings, 0 replies; 10+ messages in thread
From: FengLingDu @ 2022-04-16 13:54 UTC (permalink / raw)
  To: gdb



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.

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Program received signal SIGTRAP, Trace/breakpoint trap.
@ 2012-07-24  3:13 John Smith
  2012-07-24 17:05 ` Pedro Alves
  0 siblings, 1 reply; 10+ messages in thread
From: John Smith @ 2012-07-24  3:13 UTC (permalink / raw)
  To: gdb

hi,
    when  I  use  'step '  command  to  trace  into  a  function call
, gdb will tell me :

Program received signal SIGTRAP, Trace/breakpoint trap.

The program being debugged was signaled while in a function called from GDB.
GDB has restored the context to what it was before the call.
To change this behavior use "set unwindonsignal off".
Evaluation of the expression containing the function


then I can not  use  'next' to step out  any function call,and
'finish' command  is no usefull .




what is this  problem to be?



thanks in advance!

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: Program received signal SIGTRAP, Trace/breakpoint trap
@ 2005-09-19 16:57 Ajay Patel
  2005-09-20  5:08 ` divick kishore
  0 siblings, 1 reply; 10+ messages in thread
From: Ajay Patel @ 2005-09-19 16:57 UTC (permalink / raw)
  To: divick kishore, ramana.radhakrishnan, gdb

Hi Divik,

Are you trying to debug statically linked
application?

I see similar problem when I try to debug
NPTL based statically linked application.

Thanks
Ajay

> Hi,
>    here is my version of GDB, GCC:
> 
> GDB - 6.3
> GCC - g++ (GCC) 3.3.3 (SuSE Linux).
> Architecture -- Intel IA 64 bit,kernel --
> 2.6.5-7.193-rtgfx (SGI Altix system)
> 
> The app is 64 bit based (SGI Altix system).
> 
> I am developing a client/server application, and I am
> using some proprietary API' of SGI. 
> 
> According to gdb backtraces, I find that it crashes at
> several different places. But most of the time, it
> gets  SEGFAULT signal and the follwing message.
> 
> Program received signal SIGTRAP, Trace/breakpoint
> trap.
> [Switching to Thread 2305843009239495296 (LWP 1573)]
> <signal handler called>
> (gdb) bt
> #0  <signal handler called>
> Cannot access memory at address 0xfb0000000000528
> 
> 
> It seemed to me that somewhere some memory corruption
> is occurring, but the backtrace by gdb leaves me
> clueless. I am stuck.
> 
> Thanks,
> Divick
> 
> 
> --- Ramana Radhakrishnan
> <ramana.radhakrishnan@codito.com> wrote:
> 
> > On Mon, 2005-09-19 at 08:05 +0100, divick kishore
> > wrote:
> > > Hi,
> > >    I am getting the above error when I am trying
> > to
> > > debug a 64 but application. I have no clue why it
> > > happens. The exact message from gdb is as below.
> > Any
> > > suggestions?
> > 
> > What did you do to get this message ? A full
> > sequence of steps would be
> > useful for people to resolve your problem . And
> > please mention the
> > versions for 
> > 
> > 1. gdb 
> > 2. compiler (if GCC version of GCC) 
> > 3. The architecture under consideration . 
> > 4. Is this a 64 bit linux based app ? 
> > 
> > and then maybe someone can help you out. 
> > 
> > 
> > > 
> > > 
> > > Program received signal SIGTRAP, Trace/breakpoint
> > > trap.
> > 
> > This is just a bit too cryptic. 
> > 
> > cheers
> > Ramana
> > > 
> > > 
> > > 		
> > >
> >
> __________________________________________________________
> > 
> > > Yahoo! India Matrimony: Find your partner now. Go
> > to http://yahoo.shaadi.com
> > 
> > 
> 
> 
> 
> 		
> __________________________________________________________ 
> Yahoo! India Matrimony: Find your partner now. Go to
http://yahoo.shaadi.com
> 
> 


^ permalink raw reply	[flat|nested] 10+ messages in thread
* Program received signal SIGTRAP, Trace/breakpoint trap
@ 2003-05-15 18:44 Smita
  2003-05-15 19:21 ` Tim Combs
  0 siblings, 1 reply; 10+ messages in thread
From: Smita @ 2003-05-15 18:44 UTC (permalink / raw)
  To: gdb

Hi,
I am trying to debug a program with gdb5.3
But, I keep getting this message:
Program received signal SIGTRAP, Trace/breakpoint trap
0x0183ac7c in _sys_select ()

I keep getting this even if i continue.
Why am I seeing this? What is the solution to this?

Thanks a lot.
Smita


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2022-04-16 13:54 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-09-19  7:05 Program received signal SIGTRAP, Trace/breakpoint trap divick kishore
2005-09-19  7:56 ` Ramana Radhakrishnan
2005-09-19 10:09   ` divick kishore
  -- strict thread matches above, loose matches on Subject: below --
2022-04-16 13:54 FengLingDu
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
2003-05-15 18:44 Smita
2003-05-15 19:21 ` Tim Combs

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).