public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Enrico Piria <epiria@libero.it>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Exceptions and interrupts
Date: Mon, 23 May 2005 13:38:00 -0000	[thread overview]
Message-ID: <1116850677.19176.0.camel@hermes> (raw)
In-Reply-To: <IGXSSL$8911D16227ED0D01E713FCD210C5FB59@libero.it>

On Mon, 2005-05-23 at 11:53 +0200, Enrico Piria wrote:
> Hello.
> When an exception is triggered (especially the one that brings the GDB stub),
> should all interrupts be disabled?

Yes

> 
> Other two more generic questions are:
> 
> 1) May GDB debugging be done on a single thread,
> with other threads and interrupts enabled?
> 

This is not currently supported

> 2) May GDB debugging be done on ISRs?
> 

Yes

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
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:[~2005-05-23 12:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 13:05 Enrico Piria
2005-05-23 13:17 ` [ECOS] Etherboot Gonçalo Antunes
2005-05-23 13:38 ` Gary Thomas [this message]
2005-05-23 17:43   ` [ECOS] Simulators Andrew Armstrong
2005-05-23 18:32     ` Gary Thomas
2005-05-23 19:26       ` Andrew Armstrong
2005-05-23 23:52       ` [ECOS] Simulators Jani Monoses
2005-05-24  4:56         ` Gary Thomas

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=1116850677.19176.0.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=epiria@libero.it \
    /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).