From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Christoph Csebits <christoph.csebits@frequentis.com>
Cc: eCos mailing list <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] cyg_create_thread
Date: Tue, 04 Sep 2001 09:49:00 -0000 [thread overview]
Message-ID: <20010904184905.M7347@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <20010904180727.A31123@frequentis.com>
On Tue, Sep 04, 2001 at 06:07:27PM +0200, Christoph Csebits wrote:
> On Tue, Sep 04, 2001 at 04:55:29PM +0200, Andrew Lunn wrote:
> > > my twothreads example does not work any longer.
> > > TRACE: <1>[1068]Cyg_Check_Structure_Sizes::Cyg_Check_Structure_Sizes() Size of C struct cyg_thread != size of C++ struct Cyg_Thread
> > > ASSERT FAIL: <1>[1080]Cyg_Check_Structure_Sizes::Cyg_Check_Structure_Sizes() Size checks failed
> >
> I start with a clean build dir. But i am making some changes after
> getting the new eCos version (adding my HAL, diagnostic serial driver
> and flash support).
Well, the synthetic version compiles and runs OK.
The assertion is saying that the C struct cyg_thread, as defined in
kapidata.h is a different size to the C++ clase Cyg_Thread as defined
in thread.hxx. These two should be identical, member for member.
Maybe something is happening with the HAL specific entries in these
structures. Things like the register set? You will have to compare
then and see whats different. That should give a clue as to whats
causing the problem.
Andrew
next prev parent reply other threads:[~2001-09-04 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 7:46 Christoph Csebits
2001-09-04 7:55 ` Andrew Lunn
2001-09-04 9:07 ` Christoph Csebits
2001-09-04 9:49 ` Andrew Lunn [this message]
2001-09-04 23:35 ` [ECOS] cyg_thread vs. Cyg_Thread Christoph Csebits
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=20010904184905.M7347@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=christoph.csebits@frequentis.com \
--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).