From: Ben Warren <bwarren@qstreams.com>
To: "Martin, Tim" <tim.martin@viasat.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Debugging with no serial port
Date: Thu, 10 Aug 2006 16:53:53 -0400 [thread overview]
Message-ID: <1155243233.920.34.camel@saruman.qstreams.net> (raw)
In-Reply-To: <821B2170E9E7F04FA38DF7EC21DE487105FD14A0@VCAEXCH01.hq.corp.viasat.com>
Martin,
On Thu, 2006-08-10 at 13:12 -0700, Martin, Tim wrote:
>
> I tried this as well and have the same GDB synchronization problem e.g.
>
> break log_stuff
> commands
> silent
> if (variable_logging_enabled)
> printf "(%d,%d)\n",stuff1_variable,stuff2_variable
> end
> cont
> end
>
That's too bad. I wonder if you could run gdb from expect or some other
auto-scripting language and have it issue the 'cont' once all data is
printed (Have your code spit out a special 'end of data' delimiter).
Just a thought - no idea if it would work.
I'm not 100% certain how BDI-2000/gdb works, but I guess the gdb server
is running on the box, in which case you probably don't have much
control over how it works, and thus can't control if the output stream
is buffered or not. My BDI-2000 book doesn't have much on configuring
the gdb part.
Anyway, sorry for rambling.
regards,
Ben
next prev parent reply other threads:[~2006-08-10 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 20:12 Debugging with no serial port Martin, Tim
2006-08-10 20:53 ` Ben Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 16:30 Martin, Tim
2006-08-10 19:00 Martin, Tim
2006-08-10 19:13 ` Brian Waite
2006-08-10 17:14 Martin, Tim
2006-08-10 17:31 ` Frank
2006-08-10 19:27 ` Ben Warren
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=1155243233.920.34.camel@saruman.qstreams.net \
--to=bwarren@qstreams.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tim.martin@viasat.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 NNTP newsgroup(s).