From: Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 0/2] cryo: Re-enable checkpointing of thread area
Date: Wed, 11 Jun 2008 16:41:44 +0200 [thread overview]
Message-ID: <484FE428.3020203@bull.net> (raw)
In-Reply-To: <20080611141350.541711754-4vkkeT0zb4ZEtYaxpPmRp1aPQRlvutdw@public.gmane.org>
Benjamin Thery wrote:
> I found the cause of one of the general protection faults I saw with
> my test program and I finally managed to completely restart (a very
> dumb) program for the first time!
>
> My program was failing (GPF) at restart in glibc code. After some
> debugging I found the failures occur on SINGLE_THREAD_P calls
> (eg. glibc/sysdeps/posix/system.c:__libc_system()).
>
> I suspected a problem with nptl and remembered the comments in cr.c
> ("for redhat 9.0, NPTL") and in cr.txt ("Support linuxthreads, but not
> NPTL."). I uncommented this code that checkpoints the thread area
> (don't ask me what it is) and, voila, my program restarted!
>
> It doesn't solve everything: I still have issues restarting the 'sleep'
> program.
I spoke too fast... in fact I have no more issue with sleep or mksysvipc
programs. They both restart fine now. :)
Benjamin
--
B e n j a m i n T h e r y - BULL/DT/Open Software R&D
http://www.bull.com
prev parent reply other threads:[~2008-06-11 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 14:13 [PATCH 0/2] cryo: Re-enable checkpointing of thread area Benjamin Thery
2008-06-11 14:14 ` [PATCH 1/2] cryo: re-enable " Benjamin Thery
[not found] ` <20080611141408.977819123-4vkkeT0zb4ZEtYaxpPmRp1aPQRlvutdw@public.gmane.org>
2008-06-11 15:28 ` Serge E. Hallyn
2008-06-11 14:14 ` [PATCH 2/2] cryo: minimal test program Benjamin Thery
[not found] ` <20080611141350.541711754-4vkkeT0zb4ZEtYaxpPmRp1aPQRlvutdw@public.gmane.org>
2008-06-11 14:41 ` Benjamin Thery [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=484FE428.3020203@bull.net \
--to=benjamin.thery-6ktuutfb/bm@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
/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