From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30130 invoked by alias); 4 Jun 2008 06:40:48 -0000 Received: (qmail 30122 invoked by uid 22791); 4 Jun 2008 06:40:48 -0000 X-Spam-Check-By: sourceware.org Received: from d5152C2DE.access.telenet.be (HELO lx-dmz.televic.com) (81.82.194.222) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 04 Jun 2008 06:40:29 +0000 Received: (qmail 13578 invoked from network); 4 Jun 2008 06:39:12 -0000 Received: from nt-email.televic.com (10.0.0.9) by lx-dmz.televic.com with SMTP; 4 Jun 2008 06:39:12 -0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 04 Jun 2008 06:40:00 -0000 Message-ID: <369C2E4EDB94C34881A8178BEA192A124D9E@nt-email.TELEVIC.COM> From: =?iso-8859-1?Q?Lambrecht_J=FCrgen?= To: "Pieter-Jan Busschaert" Cc: X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] gdb output in RAM build X-SW-Source: 2008-06/txt/msg00012.txt.bz2 Hello Pieter-Jan, It is indeed our Redboot ROM that had CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS en= abled. I disabled them, but enabled CYGHWR_HAL_ARM_DUMP_EXCEPTIONS instead to see = the exceptions in "human" language instead of "GDB" language. Thanks, J=FCrgen Pieter-Jan Busschaert wrote: > 2008/5/29 J=81=FCrgen Lambrecht : >> Hello, >> >> my RAM build (redboot or ecos RAM application) prints this: >> >> $T050f:0000f071;0d:1c9d0320;#81 > > > Do you have an other bootloader on the board? In our case, this is > printed from our (ROMRAM) redboot when a processor-exception happens > in our (RAM) ecos/userprogram. Look in > hal/common/current/src/generic-stub.c, function "send_t_packet". It > first calls "__build_t_packet", which is in > hal/common/current/src/hal-stub.c > > There you can see the format is : > > T <2 digits : signal number> <2 digits : PC reg number> : contents> ; <2 digits : SP reg number> : ; # > > PC =3D program counter > SP =3D stack pointer > > There is also code to display the thread that was active, but as (in > our case) it's redboot who prints this information, there is no notion > of threads anymore at that point. We did add code there to print a > complete stack + a program-counter-backtrace (this is possible if you > have the stackpointer and know your hardware's convention for > stackframes). > > This file is compiled in when you enable > CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS (see > hal/common/current/cld/debugging.cdl). > > > kind regards, > > Pieter-Jan > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss