From: Jonathan Larmour <jlarmour@redhat.com>
To: Carlos Eduardo dos Reis Rodrigues Sobrinho <epilog@netc.pt>
Cc: eCos Discuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Problem with cosine and multithread...
Date: Thu, 01 Mar 2001 10:06:00 -0000 [thread overview]
Message-ID: <3A9E8F95.53F6CAD0@redhat.com> (raw)
In-Reply-To: <001301c0a21a$37269a20$09bd12d4@netc.pt>
Carlos Eduardo dos Reis Rodrigues Sobrinho wrote:
>
> Another question is how can I build a program without debug info and all
> that .text and place it in flash so I can do a GO 0X4(where I dl the prog)
> and ran it without the gdb if that possible.
> Thanks in advance for the help.
Build it for ROM startup and program it like you would program the GDB stub
image.
> PS: One small question.What's the difference between cyg_thread thread_s[2];
> char stack[2][4096] AND static cyg_thread thread_s[2]; static char
> stack[2][4096]; and what does volatile do in C,Sorry for the anoying
> questions that this should be for you but they aren't for me...
"static" means whether the symbols are visible outside that compilation
unit.
But don't seek help for basic C questions like this. Buy a book, don't ask
here as this list is to do with eCos only. I won't be answering any more
simple questions like that.
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-03-01 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 22:38 Carlos Eduardo dos Reis Rodrigues Sobrinho
2001-03-01 10:06 ` Jonathan Larmour [this message]
[not found] <003f01c0a225$3d6a4c00$2901a8c0@JEFF>
2001-02-28 23:01 ` Carlos Eduardo dos Reis Rodrigues Sobrinho
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=3A9E8F95.53F6CAD0@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=epilog@netc.pt \
/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).