In article [EMAIL PROTECTED],
Terry Lambert [EMAIL PROTECTED] wrote:
Vaclav Haisman wrote:
Besides, this doesn't explain anything. I see I haven't asked any question in
my previous post. So, why does FreeBSD behave different?
Because POSIX mandates that it do so?
man 3 signal tells us:
On Wed, 19 Feb 2003 08:51:23 -0800
Wes Peters [EMAIL PROTECTED] wrote:
On Wednesday 19 February 2003 04:43, Vaclav Haisman wrote:
[...]
Besides, this doesn't explain anything. I see I haven't asked any
question in my previous post. So, why does FreeBSD behave different?
Because it *is*
Hi,
I have been playing with signals handling and I've found one thing where
FreeBSD differes from other unix systems that I have access to. This test loops
endlessly in FreeBSD but terminates in SunOS 9 and GNU/Linux. It is as test for
what happens when a program raises SIGSEGV in SIGSEGV
Vaclav Haisman wrote:
I have been playing with signals handling and I've found one thing where
FreeBSD differes from other unix systems that I have access to. This test loops
endlessly in FreeBSD but terminates in SunOS 9 and GNU/Linux. It is as test for
what happens when a program raises
man 2 abort
-- Terry
logout ~/tmpman 2 abort
No entry for abort in section 2 of the manual
Besides, this doesn't explain anything. I see I haven't asked any question in
my previous post. So, why does FreeBSD behave different?
Vaclav Haisman
To Unsubscribe: send mail to [EMAIL PROTECTED]
On Wednesday 19 February 2003 04:43, Vaclav Haisman wrote:
man 2 abort
-- Terry
logout ~/tmpman 2 abort
No entry for abort in section 2 of the manual
Yeah, it's in (3). try _exit(2).
Besides, this doesn't explain anything. I see I haven't asked any
question in my previous post. So,
Thus spake Wes Peters [EMAIL PROTECTED]:
What would you like to see, a sigaction flag of SA_CRASHON2NDSIG that
is set by default? (Ah, Wes, that software comedian.)
Sure, but let's call it SA_RESETHAND. ;-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in
Vaclav Haisman wrote:
man 2 abort
-- Terry
logout ~/tmpman 2 abort
No entry for abort in section 2 of the manual
Besides, this doesn't explain anything. I see I haven't asked any question in
my previous post. So, why does FreeBSD behave different?
Because POSIX mandates that it do
Because POSIX mandates that it do so?
man 3 signal tells us:
The handled signal is unblocked when the function returns and the process
continues from where it left off when the signal occurred. Unlike previ-
ous signal facilities, the handler func() remains installed after a
Vaclav Haisman wrote:
If you want this to not happen, you should explicitly uninstall the
handler, or you should call abort(3) (or _exit(2), if you don't want
to leave a core dump).
Even though this is probably about my misunderstanding of things I post here
the test I used.
[ ... ]
10 matches
Mail list logo