Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Matthew Fyles" <Matthew.Fyles@st.com>
To: <gdb@sources.redhat.com>
Subject: Re: GDB plugin proposal
Date: Tue, 23 Apr 2002 02:16:00 -0000	[thread overview]
Message-ID: <HKEOLIPGKHGFAFAMLJKOGEBACAAA.Matthew.Fyles@st.com> (raw)

For the Superh H architecture we have added a command called fork into GDB to allow the user to create a new process from the GDB command language in the same way that the shell command is implemented.

Basically the new process gets passed a pipe to the GDB command languange when created allowing the user application to talk directly to GDB. This allows you to add new code which can be executed whilst in a GDB session without adding new commands into GDB.

The main use we have for this at the momemt is to solve the problem of having to specify a port to a simulator that is driven via the GBD server interface. We fork a loader process from GDB which sets up the sockets for communication and then passes a target-remote command with the port number back into GDB which then connects to the simulator.

This interface has proved very useful and allows us to add whatever functionality we require without changing the source code for GDB (with the exception of the 20 lines required to add the fork command)

It will also work on all supported host platforms.

If this would be useful to anybody then let me know.



             reply	other threads:[~2002-04-23  9:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  2:16 Matthew Fyles [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22 15:52 Scott Moser
2002-04-22 16:42 ` Fernando Nasser
2002-04-22 16:47   ` Fernando Nasser
2002-04-22 18:57   ` Andrew Cagney
2002-04-23  8:54   ` Scott Moser
2002-04-23 11:28     ` Daniel Berlin
2002-04-23 12:58       ` Eli Zaretskii
2002-04-23 13:07         ` Per Bothner
2002-04-23 13:19         ` Daniel Berlin
2002-04-23 22:49           ` Eli Zaretskii
2002-04-24 10:52             ` Daniel Berlin
2002-04-23 16:15       ` 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=HKEOLIPGKHGFAFAMLJKOGEBACAAA.Matthew.Fyles@st.com \
    --to=matthew.fyles@st.com \
    --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