public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jon Ringle <jon.ringle@comdial.com>
To: gdb@sources.redhat.com
Subject: tty redirection with remote target
Date: Fri, 12 Nov 2004 18:58:00 -0000	[thread overview]
Message-ID: <200411121337.48411.jon.ringle@comdial.com> (raw)

Hello,

If I invoke gdb with the tty option and connect to a remote target, the
console output from the remote target (sent with the 'O' command) is not
being redirected to the tty specified, but instead is seen in the same
console as gdb. This has a bigger impact when I try to use gdbtui. With
gdbtui, I see a blank line scroll up for every line that was sent by the
remote target.

Am I doing something wrong?

Jon

$ arm-linux-gdb --tty /dev/pts/16
GNU gdb 6.2.1
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"...
(gdb) target extended-remote /tmp/interceptty
Remote debugging using /tmp/interceptty
sip_sendToNetwork (
    buffer=0x10fd4000 "REGISTER sip:10.74.64.2 SIP/2.0\r\nFrom: 122 <sip:122@10.74.64.2>\r\nTo: <sip:122@10.74.64.2>\r\nCall-ID: 11002655231373@10.11.12.82\r\nVia: SIP/2.0/TCP 10.11.12.82:5060\r\nMax-Forwards: 70\r\nUser-Agent: HIP24-3"..., buflen=0x15b, addr=0x10f5efa0, transptype=0x1, err=0x10fd9d5c) at sipuser.c:412
412         if (!wipglobals.interface_up)
warning: shared library handler failed to enable breakpoint
(gdb) b sip_sendToNetwork
Breakpoint 1 at 0x100bdae4: file sipuser.c, line 412.
(gdb) c
Continuing.
[13:18:43.109] sipfsm: next state 12(SIP_REGISTER_WAIT_STATE), prev state 10(SIP_DISCONNECTED_STATE), pconn = 10351c00
[13:18:43.108] phonefsm: next state 2(IDLEWAITREG)
...
Breakpoint 1, sip_sendToNetwork (
    buffer=0x10fd4000 "REGISTER sip:10.74.64.2 SIP/2.0\r\nFrom: 122 <sip:122@10.74.64.2>\r\nTo: <sip:122@10.74.64.2>\r\nCall-ID: 11002663821380@10.11.12.82\r\nVia: SIP/2.0/TCP 10.11.12.82:5060\r\nMax-Forwards: 70\r\nUser-Agent: HIP24-3"..., buflen=0x15b, addr=0x10f73ac0, transptype=0x1, err=0x10fd9d5c) at sipuser.c:412
412         if (!wipglobals.interface_up)
(gdb)

                 reply	other threads:[~2004-11-12 18:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200411121337.48411.jon.ringle@comdial.com \
    --to=jon.ringle@comdial.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).