Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@celunite.com>
To: Daniel Jacobowitz <drow@false.org>,
	"Dominique Toupin (QA/EMC)" <dominique.toupin@ericsson.com>
Cc: Denis PILAT <denis.pilat@st.com>, gdb@sourceware.org
Subject: Re: Improving GDB for multicore and embedded system!
Date: Fri, 02 Mar 2007 15:04:00 -0000	[thread overview]
Message-ID: <1172847786.2170.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20070302135424.GA30113@caradoc.them.org>

Hi,

On Fri, 2007-03-02 at 08:54 -0500, Daniel Jacobowitz wrote:
> On Fri, Mar 02, 2007 at 10:08:55AM +0100, Denis PILAT wrote:
> > Today multicore debugging means multiple instance of gdb running at the 
> > same time. I don't know how possible it is to enhance gdb so that it can 
> > handle multiple programs running on different architecture.
> > I guess Daniel should have a good vision on that.
> 
> No one has ever convinced me that there's a good reason to do this,
> rather than wire up things like DSF to drive multiple GDB's, if the
> cores are not all running the same architecture and program image.  If
> they are, we generally present them as threads, and that works very
> well.
> 
> However, I have relatively little experience with non-symmetric
> multicore debugging - I have a board lab at home but it doesn't
> include any multicore targets, and we haven't done much with them at
> my job, either.  I'm always interested in learning more about new
> debugging models, or having an opportunity to do work on them.

In an earlier incarnation,  we played with getting debug working across
2 different targets ( gosh! nearly 4 years ago now) - debugging a native
x86 Linux application and the ARM Linux kernel over kgdb within the same
session. It worked ok for a prototype but then we could never get around
to doing more with it because of resource constraints and the lack of a
genuine debug use case on such a target. Getting this demo'd on a board
was a problem due to the lack of open gdb ports / JTAG interfaces for
some DSP's that were available with such SOC's then .

Another problem is the programming model on multi-cores , it varies
between platforms quite a bit - you could have a statically linked
executable with all the object files for the different cores on it built
in together - or you can have Linux apps running on something like an
ARM and a DSP application loaded separately. As you once put it in an
earlier thread -  getting the UI aspects right from the CLI as well from
MI are among the biggest challenges. 


We've had some other discussions on this list sometime in 2005. 

http://sourceware.org/ml/gdb/2005-09/msg00180.html

Don't know if you have seen them -


There is always hope that sometime someday we'll be able to do something
about this . I'll watch out for that -

My 10 paise. HTH.

-- 
cheers
Ramana

Ramana Radhakrishnan
GNU Tools
Celunite Inc (www.celunite.com)
Open Mobile Linux Platforms



  parent reply	other threads:[~2007-03-02 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 16:39 Dominique Toupin (QA/EMC)
2007-03-01 17:00 ` Dominique Toupin (QA/EMC)
2007-03-01 17:08   ` Dominique Toupin (QA/EMC)
2007-03-02  9:09 ` Denis PILAT
2007-03-02 10:04   ` Dominique Toupin (QA/EMC)
2007-03-02 13:54   ` Daniel Jacobowitz
2007-03-02 14:21     ` Fabian Cenedese
2007-03-02 14:31       ` Daniel Jacobowitz
2007-03-02 15:04     ` Ramana Radhakrishnan [this message]
2007-03-02 15:22       ` Paul Koning
2007-03-05 16:51     ` Ulrich Weigand

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=1172847786.2170.24.camel@localhost.localdomain \
    --to=ramana.radhakrishnan@celunite.com \
    --cc=denis.pilat@st.com \
    --cc=dominique.toupin@ericsson.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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