public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: RandyLin@mxic.com.tw
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Unable to run kernel test program on Samsung SNDS!
Date: Tue, 25 Nov 2003 03:47:00 -0000	[thread overview]
Message-ID: <1069732027.22988.802.camel@hermes> (raw)
In-Reply-To: <OF00EE905B.23C8E7ED-ON48256DE9.000ACC5A-48256DE9.000D8597@MXIC.COM.TW>

On Mon, 2003-11-24 at 19:28, RandyLin@mxic.com.tw wrote:
> The default value of CYGSEM_HAL_DIAG_MANGLER is GDB.
> Yes, both of application and redboot set this to GDB.
> Is this the reason that cause the ap(test program) can run on
> arm-elf-gdb but fail on redboot "load" command?
> So, I set CYGSEM_HAL_DIAG_MANGLER to NONE and recompile test program.
> test program can run on redboot "load" command, but fail on arm-elf-gdb
> Is this the correct result?
> Can I have the same image that run on both?
> Thanks!

This should not be set to anything for "user" programs.  
If things are configured properly, the application program will
inherit the I/O in the mode that it was in when the program starts.
Thus, if you use RedBoot 'load' and 'go' commands, you get plain,
non-mangled output.  If you are using GDB, you get GDB mangled output.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-11-25  3:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25  2:28 RandyLin
2003-11-25  3:47 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-26  6:51 RandyLin
2003-11-24  9:30 RandyLin
2003-11-24 10:52 ` Andrew Lunn

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=1069732027.22988.802.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=RandyLin@mxic.com.tw \
    --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).