Re: [linux-sh:03389] serial port conflicts

--ZARJHfwaSJQLOEUz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 26, 2005 at 05:25:05PM +0800, Min ZOU wrote:
> The gdb stub and gdb on host communicate via remote serial protocol.=20
> However I have a problem to debug an application program, which accesses=
=20
> the same serial port used by gdb, e.g. I/O functions like "putstring()",=
=20
> "getchar()", etc. In my case, "putstring()" cannot display any message=20
> in gdb console, and "getchar()" cannot receive any input.
>=20
> I guess there is a conflict between gdb and application program to=20
> access the same serial port. I'd like to hear any advice on solving this=
=20
> problem.
>=20
If you intend to use a gdb stub, I don't know of any way to get something l=
ike
getchar() working through it. Things like putstring() you could easily modi=
fy
to write-out a proper gdb packet with O pre-pended to write to use gdb as t=
he
console. See http://www.superhlinux.com/kgdb/gdbprotocol.php3

You can also grep the kernel for CONFIG_KGDB_CONSOLE to see some examples of
how to format the string properly.

--ZARJHfwaSJQLOEUz
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFB93SHvfgmmv+NIDsRAlaIAJ9sdQYrCib6kJwIkRmLCPK4qzsMwACgkm5i
wn0FsOhDIlN8T+QIivzYzYU=
=fSu9
-----END PGP SIGNATURE-----

--ZARJHfwaSJQLOEUz--


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl