public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: royston.choo@delphiauto.com
To: Jonathan Larmour <jlarmour@redhat.co.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] SIGTRAP, Trace/breakpoint trap
Date: Thu, 29 Jun 2000 07:04:00 -0000	[thread overview]
Message-ID: <0525690D.004D27F8.00@usabhmg99.mail.delphiauto.com> (raw)

Jonathan Larmour <jlarmour@redhat.co.uk> on 06/28/2000 20:59:30


To:   Royston Choo/Contract/US/DELCO@DELCO
cc:   ecos-discuss@sourceware.cygnus.com

Subject:  Re: [ECOS] SIGTRAP, Trace/breakpoint trap



royston.choo@delphiauto.com wrote:
>>
>> Has anyone seen SIGTRAP error while running (continue) GDB Insight?
>> error message: "Program received signal SIGTRAP, Trace/breakpoint trap"
>>
>> I thought it could be an exception, where can I trace down this trap?

>This generally happens because the program has hit a breakpoint where GDB
>doesn't think there should be one. A common case is if the board resets, at
>which point the boot ROM on the board will deliberately hit a breakpoint
>instruction (on most targets anyway).

>Another common case is if the application does not co-operate with the GDB
>stub in the ROM, _and_ the application doesn't have GDB stubs embedded
>itself. If this is the case, generally you can successfully hit *one*
>breakpoint, but never continue successfully from it. The fix is to include
>GDB stubs in your app by enabling the appropriate option in the eCos
>config.

>To give a more definite answer, of course, I'd need to know your target,
>platform, eCos version, ROM stub, whether you have GDB stubs included or
>not, and in exactly what situation this happens anyway :-).

I am using the DK177 target board running NEC V850-SB1 processor. eCos version
1.3.10.
GDB stub is downloaded into the processor.

I had added a GPIO driver package into the eCos config., yet to be tested.
Also created a simple test program, test.exe.

Having downloaded and run the test.exe, hitting 'continue' will generate a
SIGTRAP.
SIGTRAP will keep on coming up as long as I hit 'continue'.


Royston






Received: from plmlir3.mail.eds.com ([205.191.22.43]) by
usabhmg98.mail.delphiauto.com (Lotus SMTP MTA v4.6.5  (863.2 5-20-1999)) with
SMTP id 0525690D.000AFFB2; Wed, 28 Jun 2000 21:00:08 -0500
Received: from plmlir3.mail.eds.com (localhost [127.0.0.1])
     by plmlir3.mail.eds.com (8.9.3/8.9.3) with ESMTP id WAA10905
     for <royston.choo@delphiauto.com>; Wed, 28 Jun 2000 22:00:09 -0400 (EDT)
Received: from plmlir3.mail.eds.com (localhost [127.0.0.1])
     by plmlir3.mail.eds.com (8.9.3/8.9.3) with ESMTP id VAA10540
     for <royston.choo@delphiauto.com>; Wed, 28 Jun 2000 21:59:34 -0400 (EDT)
Received: from plmler1.mail.eds.com (plmler1.mail.eds.com [199.228.142.73])
     by plmlir3.mail.eds.com (8.9.3/8.9.3) with ESMTP id VAA10536
     for <royston.choo@delphiauto.com>; Wed, 28 Jun 2000 21:59:34 -0400 (EDT)
Received: from pasanda.cygnus.co.uk (dns.cygnus.co.uk [194.130.39.3])
     by plmler1.mail.eds.com (8.9.3/8.9.3) with SMTP id VAA27742
     for <royston.choo@delphiauto.com>; Wed, 28 Jun 2000 21:59:33 -0400 (EDT)
Received: (qmail 26458 invoked by alias); 29 Jun 2000 01:59:31 -0000
Received: (qmail 26449 invoked from network); 29 Jun 2000 01:59:30 -0000
Received: from murgh.cygnus.co.uk (HELO redhat.co.uk) (jlarmour@194.130.39.56)
  by dns.cygnus.co.uk with SMTP; 29 Jun 2000 01:59:30 -0000
Sender: jlarmour@cygnus.co.uk
Message-ID: < 395AAD82.BEA9247D@redhat.co.uk >
Date: Thu, 29 Jun 2000 02:59:30 +0100
From: Jonathan Larmour <jlarmour@redhat.co.uk>
Organization: Red Hat UK Ltd.
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.14-11smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: royston.choo@delphiauto.com
CC: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] SIGTRAP, Trace/breakpoint trap
References: < 0525690D.000984D4.00@usabhmg99.mail.delphiauto.com >
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


|--------------------------------------->
|usabhmg98/g/server/delphiauto          |
|usabhhu98/h/server/delphiauto          |
|USKOKH01/DELCO                         |
|USKOKHM1/DELCO                         |
|USKOKM14/DELCO                         |
|--------------------------------------->
  >---------------------------------------|
  |06/28/2000 21:00:11 - 06/28/2000       |
  |21:00:11                               |
  |06/28/2000 21:58:10 - 06/28/2000       |
  |21:58:11                               |
  |06/28/2000 21:00:11 - 06/28/2000       |
  |21:00:13                               |
  |06/28/2000 21:00:13 - 06/28/2000       |
  |21:00:14                               |
  |06/28/2000 20:59:43 - 06/28/2000       |
  |20:59:44                               |
  >---------------------------------------|









Joo Meng Choo (Royston)

------------------------------------------------------------
        Mobile Multimedia Group
        Delphi Delco Electronics Systems
        Delphi Automotive Systems
        Office: 1-765-4511745
        Location: Plant 10, R302

        royston.choo@delphiauto.com
        http://www.angen.net/~Royston



             reply	other threads:[~2000-06-29  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-29  7:04 royston.choo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-28 18:44 royston.choo
2000-06-28 18:59 ` Jonathan Larmour

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=0525690D.004D27F8.00@usabhmg99.mail.delphiauto.com \
    --to=royston.choo@delphiauto.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.co.uk \
    /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).