public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "fairy" <yyt@os.pku.edu.cn>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Microwindows on eCos
Date: Sun, 06 Apr 2003 08:05:00 -0000	[thread overview]
Message-ID: <002e01c2fc14$0e052980$d601a8c0@osa1> (raw)

Hi, 

I'm trying to run microwindows on eCos on linux synthetic target but meet with some problems. 

Firstly, if I just make a linux synthetic target without any template, I cannot successfully add the microwindows package even thought I resolve all the conflicts. Many problems concerning the network files are reported in compling procedure. 

Then I add the microwindows package with elix template. It is successfully built but nothing happens when I run the executable file--it fails to start the window. (The test program is "demo.c" which I get from the microwindows package.) 

So I trace it with insight. I find that whenever it comes to 
ACCESS_PER_THREAD_DATA() 
"data->_nxSocket" will gain a great value 1919448176 where "data" is a structure to store datas from a thread. 

Problem occures when such "data->_nxSocket" is used as index of an array contains 16 elements: 
cyg_file *fp=desc[fd]; 

I have no idea what the problem is. Can anyone give me some advices? Thanks a lot!! 

Regards, 
fairy

             reply	other threads:[~2003-04-06  8:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06  8:05 fairy [this message]
2003-04-07 22:17 ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2008-02-27 17:05 Antoine.Amirault
2003-07-17 15:59 [ECOS] MicroWindows " Chris Garry
2003-07-17 16:17 ` Bob Koninckx
2003-07-17 16:43   ` Chris Garry
2003-07-18  4:40 ` Jonathan Larmour
2003-07-18 15:51   ` Chris Garry
2001-04-12 14:36 [ECOS] Microwindows " 宋宜叡
2001-04-13  6:55 ` Gary Thomas
2001-03-02  6:05 Rosimildo daSilva
2001-03-01 14:34 Rosimildo daSilva
2001-03-02  1:53 ` wangwei
2001-03-02  2:42   ` Rafael Rodríguez Velilla
2001-03-02  2:57     ` Martin van Veen
2001-03-02  3:48     ` Christian Plessl
2001-01-16  2:46 Á¶¼¼Çü
2001-02-28 17:47 ` wangwei
2001-03-01  4:01   ` Robin Farine

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='002e01c2fc14$0e052980$d601a8c0@osa1' \
    --to=yyt@os.pku.edu.cn \
    --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).