Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: multi-process remote protocol extensions
Date: Fri, 30 May 2008 13:15:00 -0000	[thread overview]
Message-ID: <1212083885.3601.179.camel@localhost.localdomain> (raw)
In-Reply-To: <200805272233.24078.pedro@codesourcery.com>


Hi Pedro, 

I'd like to throw out some thoughts *before* I read your 
somewhat long but apparently well-thought-out proposal.
I'll be brief.

Forgive me if what I toss out has already been covered.

Have you considered the cross-over between the general
case of debugging multiple processes, and the more restricted
case of debugging forks of the same process?  With forks,
(and excluding exec for the moment), you actually have 
several processes with separate address spaces but one
common symbol table.

I'm thinking that the support for fork debugging that we
already have might serve as a stepping-off point for what
you propose.

Maybe an incremental step would be to extend the fork
debugging functionality into the remote protocol and
get it to work with gdbserver?

I'll just go off and actually read what you wrote now...
;-)
Michael




  reply	other threads:[~2008-05-29 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 17:18 Pedro Alves
2008-05-30 13:15 ` Michael Snyder [this message]
2008-05-30 13:35   ` Pedro Alves
2008-06-03  1:28 ` Daniel Jacobowitz
2008-06-03 15:20   ` Pedro Alves
2008-06-03 15:42     ` Daniel Jacobowitz
2008-06-03 15:55       ` Pedro Alves
2008-06-03 16:14         ` Daniel Jacobowitz
2008-06-03 17:04           ` Pedro Alves
2008-06-03 17:12             ` Pedro Alves
2008-06-03 17:31               ` 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=1212083885.3601.179.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=gdb@sourceware.org \
    --cc=pedro@codesourcery.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