From: Jonathan Larmour <jlarmour@redhat.com>
To: bgat@open-widgets.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Turn off gdb console?
Date: Tue, 30 Jan 2001 19:07:00 -0000 [thread overview]
Message-ID: <3A77816B.EE5B07F1@redhat.com> (raw)
In-Reply-To: <20010130164509.B13358@sr1.open-widgets.com>
bgat@open-widgets.com wrote:
>
> Hi! Quick question...
>
> I'm trying to run the test applications in the latest eCos CVS
> repository, like dhrystone, over ethernet using RedBoot on the MBX.
> As expected, whenever there's a printf() in dhrystone, it shows up on
> the serial port, formatted as a gdb "console output" message.
>
> This behavior would make sense if I was talking to the MBX target over
> the serial port, but I'm not. Furthermore, what I would like to see
> is raw, streaming output from dhrystone on the serial port; I want to
> control the application via ethernet, but not have the console tied to
> gdb's console.
>
> I gave my ecos.ecc file a quick skim, and didn't come across anything
> that was obviously related to console output formatting. What's the
> CYG_xxx that I use?
Believe it or not, we're just working on a generic solution to this type of
situation that will allow a loaded application to claim the
console/debugging virtual vectors
But for now I believe you should be able to enable the option
CYGDBG_HAL_DIAG_DISABLE_GDB_PROTOCOL, which should turn off GDB packet
encoding in the MBX hal diag output (assuming you have not explicitly
enabled virtual vector diag).
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-01-30 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 14:45 bgat
2001-01-30 19:07 ` Jonathan Larmour [this message]
2001-01-31 13:19 ` bgat
2001-01-31 13:41 ` [ECOS] GDB stubs build problem for vrc4373 Ling Su
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=3A77816B.EE5B07F1@redhat.com \
--to=jlarmour@redhat.com \
--cc=bgat@open-widgets.com \
--cc=ecos-discuss@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).