From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [bug?] strange behaviour with longjmp, itimer, and read/recv (but not pause)
Date: Thu, 20 Jan 2005 15:53:59 -0600 [thread overview]
Message-ID: <41F02877.5010508@nortelnetworks.com> (raw)
In-Reply-To: <41F026E1.5050006@nortelnetworks.com>
Friesen, Christopher [CAR:VC21:EXCH] wrote:
> It this point I suspected my setjmp/longjmp code was bad, so to test it
> I changed the recv() call to a pause() call. After that change,
> everything worked fine. I changed it to a read() call, and it breaks
> again with the third signal never being delivered.
My bad, didn't notice that pause() doesn't get restarted. So the
setjmp/longjmp code isn't being called with pause.
Also, behaviour is the same with 2.6.5 on a P4.
Chris
next prev parent reply other threads:[~2005-01-20 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 21:47 [bug?] strange behaviour with longjmp, itimer, and read/recv (but not pause) Chris Friesen
2005-01-20 21:53 ` Chris Friesen [this message]
2005-01-20 22:09 ` [bug?] strange behaviour with longjmp, itimer, and read/recv (but not pause) -- solved Chris Friesen
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=41F02877.5010508@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.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