public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Anupama Chandwani <anupama.chandwani@gmail.com>
To: drow@false.org, gdb@sources.redhat.com
Subject: Re: Is multiprocessor debugging multithreaded debugging?
Date: Wed, 28 Sep 2005 09:06:00 -0000	[thread overview]
Message-ID: <689eb347050928020544f90509@mail.gmail.com> (raw)

In continuation with my prev mail..
I want to extend gdb to debug homing ogenous multiprocessor system
(say multiple ARM or x86 processors on single chip) by remote
debugging in a single session of gdb.

What i want to know is are there enough applications being written on
such multi processors? Also are there different executables being
required to be debugged simultaneously? Coz this is what i want to
extend in further.. Each processor running a different executable so
the processors dont share memory & run with different images of code.

An application of such debugger could be while building an OS but that
wouldnt involve different executables.. So are there applications
requiring to run different executables on each processor? Say for
example a prog gives a certain bug on when there is certain other
program running on the other processor or something similar to
this....

As far as i know this done by multiplexing the JTAG interface (for
x86) &different sessions of gdb right now. Any other? And any flaws or
inconvenience with present methods?

Regards,
anupama

             reply	other threads:[~2005-09-28  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28  9:06 Anupama Chandwani [this message]
2005-09-28 10:17 ` Steven Johnson
2005-09-28 11:13   ` Ramana Radhakrishnan
2005-09-28 13:32     ` Steven Johnson
2005-09-28 17:24       ` Ramana Radhakrishnan
  -- strict thread matches above, loose matches on Subject: below --
2005-09-24  6:56 Anupama Chandwani
2005-09-24 15:14 ` Daniel Jacobowitz
2005-09-24 17:24   ` Aaron S. Kurland
2005-09-24 19:06     ` Daniel Jacobowitz

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=689eb347050928020544f90509@mail.gmail.com \
    --to=anupama.chandwani@gmail.com \
    --cc=drow@false.org \
    --cc=gdb@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).