From: veenu khanna <veenu_khanna@yahoo.com>
To: gdb@sourceware.org
Subject: GDB Stub & GPL question
Date: Wed, 31 Jan 2007 15:02:00 -0000 [thread overview]
Message-ID: <256227.64036.qm@web53809.mail.yahoo.com> (raw)
Hello
I have a question regarding implementing a remote stub. Say we have to implement/extend a stub for x86 architecture with our own OS.
IN section for "Implementing a remote stub (Section 17.5.3)" in "Debugging with GDB" document there is a point
"Make sure you have a serial connection between your target machine and the gdb host,
and identify the serial port on the host."
Does this mean that GDB on host and GDB agent/stub on the target can only talk on a serial port ?
And in point 7 it says "Start gdb on the host, and connect to the target" in which TCP connection is allowed as well.
Can someone help me in getting things right ?
I know that it is possible to have a TCP communication between gdb and gdbserver.
Is there a support for the same for stubs ?
Another question is regarding GPL...
some part of stub code will be residing in our kernel which is proprietary.
Does that mean we will have to release the code for kernel as well ?
Thanx
Veenu
____________________________________________________________________________________
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367
next reply other threads:[~2007-01-31 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 15:02 veenu khanna [this message]
2007-01-31 15:04 ` Daniel Jacobowitz
2007-01-31 19:10 ` Nicholas Mc Guire
2007-01-31 19:13 ` Daniel Jacobowitz
2007-02-01 1:12 ` Robert Dewar
2007-02-01 5:26 ` Nicholas Mc Guire
2007-02-01 9:44 ` Robert Dewar
2007-02-01 22:51 ` Mark Kettenis
2007-02-09 15:21 veenu khanna
2007-02-09 15:34 ` Daniel Jacobowitz
2007-02-09 15:35 ` Paul Koning
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=256227.64036.qm@web53809.mail.yahoo.com \
--to=veenu_khanna@yahoo.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