public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001466] /dev/null serial driver
Date: Thu, 16 Feb 2012 15:58:00 -0000	[thread overview]
Message-ID: <20120216155747.866B92F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001466-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001466

--- Comment #9 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2012-02-16 15:57:43 GMT ---
(In reply to comment #6)

> Maybe the proper solution is in the stdio lib?

My check for eCos fopen("/dev/null", ...) from the box

The eCos template:

  cdl_configuration eCos {
      template    default ;
      package CYGPKG_IO_FILEIO current ;
  };

Example of GDB session:

  % arm-eabi-gdb -q examples/hello
  (gdb) target remote /dev/ttyUSB0
  Remote debugging using /dev/ttyUSB0
  0x00002d48 in ?? ()
  (gdb) load
  Loading section .rom_vectors, size 0x40 lma 0x81008000
  Loading section .text, size 0x9714 lma 0x81008040
  Loading section .rodata, size 0x344 lma 0x81011754
  Loading section .data, size 0x484 lma 0x81011a98
  Start address 0x81008040, load size 40732
  Transfer rate: 3 KB/sec, 299 bytes/write.
  (gdb) b main
  Breakpoint 1 at 0x81008534: file hello.c, line 7.
  (gdb) b exit
  Breakpoint 2 at 0x81010ad0: file
/home/sg/repo/ecos-hg/packages/language/c/libc/startup/current/src/exit.cxx,
line 74.
  (gdb) cont
  Continuing.
  [New Thread 2]
  [Switching to Thread 2]

  Breakpoint 1, main () at hello.c:7
  7        FILE           *fh = fopen("/dev/null", "r+");
  (gdb) l
  2    #include <stdlib.h>
  3    
  4    int
  5    main(void)
  6    {
  7        FILE           *fh = fopen("/dev/null", "r+");
  8        fprintf(stdout, "Hello, eCos world! (at stdout)\n");
  9        fprintf(fh, "Hello, eCos world! (at /dev/null)\n");
  10        fclose(fh);
  11        fprintf(stdout, "Bye! (at stdout)\n");
  (gdb) cont
  Continuing.
  Hello, eCos world! (at stdout)
  Bye! (at stdout)

  Breakpoint 2, exit (status=0)
      at
/home/sg/repo/ecos-hg/packages/language/c/libc/startup/current/src/exit.cxx:74
  74    exit( int status )
  Current language:  auto; currently c++
  (gdb) 

And what you get?

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-02-16 15:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 17:39 [Bug 1001466] New: " bugzilla-daemon
2012-01-27 19:14 ` [Bug 1001466] " bugzilla-daemon
2012-02-15 13:47 ` bugzilla-daemon
2012-02-15 13:48 ` bugzilla-daemon
2012-02-15 20:46 ` bugzilla-daemon
2012-02-16  9:55 ` bugzilla-daemon
2012-02-16 14:01   ` Grant Edwards
2012-02-16 12:20 ` bugzilla-daemon
2012-02-16 14:21 ` bugzilla-daemon
2012-02-16 15:06 ` bugzilla-daemon
2012-02-16 15:39 ` bugzilla-daemon
2012-02-16 15:58 ` bugzilla-daemon [this message]
2012-02-16 16:26 ` bugzilla-daemon
2012-02-16 16:37 ` bugzilla-daemon
2012-02-16 16:49 ` bugzilla-daemon
2012-02-16 17:21 ` bugzilla-daemon
2012-02-17  6:17 ` bugzilla-daemon
2012-02-18 19:38 ` bugzilla-daemon

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=20120216155747.866B92F78001@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.org \
    /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).