From: Blaisorblade <blaisorblade@yahoo.it>
To: Allan Graves <allan.graves@oracle.com>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Clearing kmalloc_ok during shutdown is broken - malloc will clear our data.
Date: Mon, 3 Oct 2005 20:48:23 +0200 [thread overview]
Message-ID: <200510032048.23868.blaisorblade@yahoo.it> (raw)
In-Reply-To: <434134CF.7040108@oracle.com>
On Monday 03 October 2005 15:40, Allan Graves wrote:
> I'm not understanding why glibc would break the registers at will.
> From setjmp:
> /* NOTE: The machine-dependent definitions of `__sigsetjmp'
> assume that a `jmp_buf' begins with a `__jmp_buf' and that
> `__mask_was_saved' follows it. Do not move these members
> or add others before it. */
> Seems to indicate to me that this isn't gonna change,
the comments above are mostly relative to the definitions of __sigsetjmp, i.e.
to glibc internal code. Also, it's related to the layout of the structure,
while our main problem is not the structure layout.
> and I'm using the
> bits/setjmp.h defines, so if they do change, the code should just follow
> along with the change. Am I missing something?
I didn't even see those constants - I stopped earlier, at __jmp_buf_tag. Given
that it feels like a Glibc private thing, I worried.
Since those constants are explicitly exported, I guess that's for userspace
programs as well, so Glibc provides that API as a public one.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-10-03 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 11:46 [uml-devel] Clearing kmalloc_ok during shutdown is broken - malloc will clear our data Blaisorblade
2005-09-28 20:12 ` Jeff Dike
2005-09-29 12:07 ` Blaisorblade
2005-09-28 21:31 ` Jeff Dike
2005-09-29 14:14 ` Blaisorblade
2005-10-02 1:08 ` Jeff Dike
2005-10-02 10:31 ` Blaisorblade
2005-10-02 18:27 ` Jeff Dike
2005-10-03 13:40 ` Allan Graves
2005-10-03 18:48 ` Blaisorblade [this message]
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=200510032048.23868.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=allan.graves@oracle.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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