public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: divick kishore <divick_kishore@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: Program received signal SIGTRAP, Trace/breakpoint trap
Date: Mon, 19 Sep 2005 07:56:00 -0000	[thread overview]
Message-ID: <1127116589.22215.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20050919070526.34007.qmail@web60624.mail.yahoo.com>

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

  reply	other threads:[~2005-09-19  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19  7:05 divick kishore
2005-09-19  7:56 ` Ramana Radhakrishnan [this message]
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

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1127116589.22215.19.camel@localhost.localdomain \
    --to=ramana.radhakrishnan@codito.com \
    --cc=divick_kishore@yahoo.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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