public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Stefan Syberichs <Stefan.Syberichs@ascom.ch>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Debugging multi-threaded eCos application using GDB
Date: Fri, 03 Aug 2001 06:21:00 -0000	[thread overview]
Message-ID: <3B6AA556.116C3DA4@redhat.com> (raw)
In-Reply-To: <OF834BFF37.952BB457-ONC1256A9D.00346E1C@hasler.ascom.ch>

Stefan Syberichs wrote:
> 
> Hello,
> 
> We have a similar problem like Nadine:
> Debugging an eCos application for the linux target is hard, because gdb is
> not aware of
> the eCos threads.
> 
> > We do have some ideas on how to fix this properly, basically making
> > the thread-aware debugging inside gdb much more flexible, but so far
> > nobody has been willing to contribute or fund any of the work
> > involved.
> 
> > Bart
> 
> Bart, what exactly are the ideas for gdb ? Or does anybody have a solution
> meanwhile ?

Actually I would have thought the easiest route would be to allow included
stubs in the synth target to be available at a socket, and then using the
remote protocol. Making it available as a socket should "just" be a case of
adding a virtual vectored comm interface. It's probably a bit too much work
for us to just do for fun, particularly since the synth target doesn't use
virtual vectors at all right now.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-08-03  6:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03  2:49 Stefan Syberichs
2001-08-03  6:21 ` Jonathan Larmour [this message]
2001-08-03  7:39 ` Bart Veer
2001-08-03  8:11   ` Jonathan Larmour
2001-08-03  9:46     ` Bart Veer
  -- strict thread matches above, loose matches on Subject: below --
2001-04-23  0:28 Nadine.Albiez-extern
2001-04-23  5:52 ` Bart Veer

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=3B6AA556.116C3DA4@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=Stefan.Syberichs@ascom.ch \
    --cc=ecos-discuss@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).