Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-22 Thread John Polstra
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 sign

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-20 Thread Sebastian Lederer
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

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread Terry Lambert
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. [ .

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread Vaclav Haisman
> 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 a

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread Terry Lambert
Vaclav Haisman wrote: > > man 2 abort > > > > -- Terry > > logout ~/tmp>man 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

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread David Schultz
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"

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread Wes Peters
On Wednesday 19 February 2003 04:43, Vaclav Haisman wrote: > > man 2 abort > > > > -- Terry > > logout ~/tmp>man 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

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread Vaclav Haisman
> man 2 abort > > -- Terry logout ~/tmp>man 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

Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread Terry Lambert
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 S

Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop

2003-02-19 Thread Vaclav Haisman
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 handle