From: paawan oza <paawan1982@yahoo.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
Michael Snyder <msnyder@vmware.com>
Subject: Re: debugging gdb using gdb
Date: Sat, 19 Feb 2011 04:51:00 -0000 [thread overview]
Message-ID: <913587.17568.qm@web112517.mail.gq1.yahoo.com> (raw)
can I get some inputs regarding following mail chain ?
as debugging gdb using gdb on arm is becoming difficult.
Regards,
Oza.
----- Original Message ----
From: paawan oza <paawan1982@yahoo.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Sent: Thu, February 17, 2011 9:01:12 AM
Subject: Re: debugging gdb using gdb
it works absolutely fine on x86 linux.
on both terminals gdb allows input output at any time.
the difference is;
in arm-linux I connect through telnet
while in x86-linux, just local native terminal.
Regards,
Oza.
----- Original Message ----
From: Michael Snyder <msnyder@vmware.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Sent: Wed, February 16, 2011 11:38:25 PM
Subject: Re: debugging gdb using gdb
paawan oza wrote:
> Hi,
>
> during reversible implementation, I am trying to debug arm-gdb using arm-gdb.
> so i connect through telnet terminal and open two different terminals.
> and run both the gdb on target and attach the one gdb with another one.
> the moment I attach another gdb and give continue command, the gdb being
>debugged, looses iis terminal, and I am not able to type anything, and gdb does
>not accept any keyboard input and it hangs.
>
> Regards,
> Oza.
What happens if you try the same thing on x86 linux?
next reply other threads:[~2011-02-19 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 4:51 paawan oza [this message]
2011-02-19 22:30 ` Michael Snyder
2011-02-21 8:41 ` paawan oza
-- strict thread matches above, loose matches on Subject: below --
2011-02-16 3:42 paawan oza
2011-02-16 18:08 ` Michael Snyder
2011-02-17 3:31 ` paawan oza
2011-02-20 8:07 ` Jan Kratochvil
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=913587.17568.qm@web112517.mail.gq1.yahoo.com \
--to=paawan1982@yahoo.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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