public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
Cc: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: hello world app SEG faults with Linux synth target
Date: Tue, 21 Jul 2009 09:41:00 -0000	[thread overview]
Message-ID: <4A658D37.9050101@dallaway.org.uk> (raw)
In-Reply-To: <b18c5f790907210110r78e4cef6l16164637637f0987@mail.gmail.com>

Mandeep Sandhu wrote:

>>> Any clues how to fix this?
>>>
>>> How does the hello world app make use of the ecosynth app?
>> You should not need the I/O auxiliary process for a "hello world"
>> application.
> 
> Ok. So the printf's would use the std in/out/err file descriptors offered
> to the ecos process by Linux?

printf() output should go to stdout by default.

>> Which Linux distribution and version are you using?
> 
> uname -a:
> Linux mindstorm 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51
> UTC 2009 i686 GNU/Linux
>> If you are running on Debian or Ubuntu, try adding
>> "-fno-stack-protector" to CYGBLD_GLOBAL_CFLAGS. Ref:
>>
>>  http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000801
>>
>> You will need to "make clean" and rebuild eCos.
> 
> Just did that and it seems to work...though I don't see the printf's
> on the console and the app does not exit!

Running the "stdiooutput" test (without "--io") works for me on CentOS
5. Test output is on stdout and the test exits normally.

John Dallaway

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

  reply	other threads:[~2009-07-21  9:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21  6:30 [ECOS] " Mandeep Sandhu
2009-07-21  7:30 ` Sergei Gavrikov
     [not found]   ` <b18c5f790907210111k3a4643adg80003969e2bf0520@mail.gmail.com>
2009-07-21  8:43     ` Sergei Gavrikov
2009-07-21  9:05       ` Sergei Gavrikov
2009-07-21 11:00         ` Mandeep Sandhu
2009-07-21 11:18           ` Sergei Gavrikov
     [not found]             ` <b18c5f790907210442q59e83781lf138151b37244a53@mail.gmail.com>
2009-07-21 12:29               ` Sergei Gavrikov
2009-07-21 14:01                 ` Mandeep Sandhu
2009-07-21 14:11                   ` Sergei Gavrikov
2009-07-22  8:55                 ` Mandeep Sandhu
2009-07-22 10:45                   ` Sergei Gavrikov
2009-07-22 10:54                     ` Mandeep Sandhu
2009-07-22 14:05                       ` Mandeep Sandhu
2009-07-22 14:10                         ` Sergei Gavrikov
2009-07-23  8:04                           ` Mandeep Sandhu
2009-07-23  8:20                             ` Sergei Gavrikov
2009-07-23  9:36                               ` Mandeep Sandhu
2009-07-23  9:46                                 ` Sergei Gavrikov
2009-07-23 10:34                                   ` Mandeep Sandhu
2009-07-23 11:03                                     ` Mandeep Sandhu
2009-07-23 11:11                                       ` Sergei Gavrikov
2009-07-23 11:21                                         ` Sergei Gavrikov
2009-07-23 11:39                                           ` Mandeep Sandhu
2009-07-23 11:45                                             ` Sergei Gavrikov
2009-07-23 13:18                                               ` Mandeep Sandhu
2009-07-23 13:35                                                 ` Sergei Gavrikov
2009-07-21  9:29       ` Sergei Gavrikov
2009-07-21 10:51         ` Mandeep Sandhu
2009-07-21  7:46 ` [ECOS] " John Dallaway
2009-07-21  8:10   ` Mandeep Sandhu
2009-07-21  9:41     ` John Dallaway [this message]
2009-07-21 10:50       ` Mandeep Sandhu

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=4A658D37.9050101@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=mandeepsandhu.chd@gmail.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).