From: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>
To: Dan Conti <danc@iobjects.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Error modifiying Cyg_Thread class...
Date: Sat, 07 Jul 2001 13:40:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.20.0107071335500.23774-100000@washoe.ics.uci.edu> (raw)
In-Reply-To: <D8DFF0AFE792914996F997E68FEC3A48F2BF@bunker.iobjects.com>
> One thing to note, if you enable assertions in your kernel then things
> like this will cause a halt, since there are a bunch of assertions to
> check structure vs. class sizes at startup.
>
> -Dan
How do a get away from this? Can I add assertions for the new members? Can
I modify such assertions so that the new members are considered?
Thanks for replying,
Cristiano.
next prev parent reply other threads:[~2001-07-07 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 12:59 Dan Conti
2001-07-07 13:40 ` Cristiano Ligieri Pereira [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-07 13:48 Dan Conti
2001-07-07 9:28 Cristiano Ligieri Pereira
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=Pine.SOL.4.20.0107071335500.23774-100000@washoe.ics.uci.edu \
--to=cpereira@ics.uci.edu \
--cc=danc@iobjects.com \
--cc=ecos-discuss@sourceware.cygnus.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).