public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: trollepi jj <jackoaway@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] how work synthetic for exceptions
Date: Thu, 03 Apr 2008 12:56:00 -0000	[thread overview]
Message-ID: <20080403124803.GO9320@lunn.ch> (raw)
In-Reply-To: <BAY121-W43C92BE891048CDF3A26E2ADF70@phx.gbl>

On Thu, Apr 03, 2008 at 01:01:11PM +0100, trollepi jj wrote:
> 
> Hi,
> I try do modify the execution of a thread for the synthetic target.
> I've done that for an at91 board (using SWI,exception hanler and HAL_SavedRegisters to store the context info).
> I put an exception handler for the CYG_HAL_SYS_SIGILL to see if i get the info pointers of the handler (3rd parameter of the function).

A normal signal handler does not have access to the registers for the
normal program flow when the signal went off. However, there is often
an undocumented way to get access to this. Take a look at:

http://www.tlug.org.za/wiki/index.php/Obtaining_a_stack_trace_in_C_upon_SIGSEGV

Using this it might be able to generate a HAL_SavedRegisters set.

      Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2008-04-03 12:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 12:26 trollepi jj
2008-04-03 12:38 ` Gary Thomas
2008-04-03 12:48   ` trollepi jj
2008-04-03 12:56 ` Andrew Lunn [this message]
2008-04-03 13:24   ` trollepi jj
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 12:01 trollepi jj
2008-04-03 14:08 ` Bart Veer
2008-04-09  9:10   ` trollepi jj
2008-04-09  9:46     ` Andrew Lunn

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=20080403124803.GO9320@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jackoaway@hotmail.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).