Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: gdb@sourceware.org
Subject: Re: Multiprogram teaser
Date: Tue, 29 Jul 2008 13:14:00 -0000	[thread overview]
Message-ID: <1217319521.2841.18.camel@thomas> (raw)
In-Reply-To: <488E7670.40609@codesourcery.com>

On Mon, 2008-07-28 at 18:46 -0700, Stan Shebs wrote: 
> Here's a little teaser showing the results of me flogging GDB's source 
> code. In addition to the fun aspect of listing the main()s of two 
> different programs, it points up the the potential confusion of having 
> several programs in a session. What I've got so far in my prototype is 
> the ability to collect multiple execs from the command line, the 
> creation of "exec" objects from which you can select one as "current", 
> and some symbol table hacking to restrict lookups to the current executable.

Hi Stan,

This looks good, but points up the limitations of line based debugging
once you have to handle multiple processors. Realistically this sort of
approach is going to need some sort of windowing environment to separate
out the information. Do you have a view of how this might look inside
gdbtui or ddd or Eclipse? It might be worth thinking about how GDB would
look debugging a modern mobile phone, with perhaps 5 processors, each
from a different manufacturer.

Best wishes,


Jeremy

-- 
Tel:      +44 (1202) 416955
Cell:     +44 (7970) 676050
SkypeID: jeremybennett
Email:   jeremy.bennett@embecosm.com
Web:     www.embecosm.com



  parent reply	other threads:[~2008-07-29  8:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  2:29 Stan Shebs
2008-07-29  8:18 ` Michael Snyder
2008-07-29 13:14 ` Jeremy Bennett [this message]
2008-07-29 13:34   ` Marc Khouzam
2008-07-29 13:51     ` Pedro Alves
2008-07-29 14:58       ` Marc Khouzam
2008-07-29 14:12     ` Stan Shebs
2008-07-29 16:02       ` Marc Khouzam
2008-07-30 17:21       ` Tom Tromey
2008-07-30 17:43 ` Tom Tromey
2008-07-30 18:07   ` Stan Shebs

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=1217319521.2841.18.camel@thomas \
    --to=jeremy.bennett@embecosm.com \
    --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