GDB Stub & GPL question

[Nicholas Mc Guire]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> On Wed, Jan 31, 2007 at 07:02:04AM -0800, veenu khanna wrote:
>> 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 ?
>>
>> 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 ?
>
> If you copy the stub from the GDB source tree, then yes you would
> have a GPL problem.  I recommend writing one from scratch, instead,
> based on the documentation - that's what most people seem to do.
> The examples in GDB are quite old.
>
thats stange - considering the boilerplate on gdb-6.6/gdb/*-stub.c
clearly stating:


                 THIS SOFTWARE IS NOT COPYRIGHTED


how does that fit with there being a GPL problem ? - if there really is
then these headers sould be changed as the expectation is clearly 
different.

hofrat
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFFwN0rnU7rXZKfY2oRAnzRAJ401TITCfM+qMaNkuYi/QKnOo174gCfWeIM
GgGViqckwv7Fy99KGVCvaQY=
=8U8j
-----END PGP SIGNATURE-----