>
> Dodge Ram wrote:
>
> > Also, is there a list of reasons for a SIGSEGV ?
>
> Only one: "Your program is buggy" :-)
>
> - mark
I've actually got a SIGSEGV/SIGBUS handler in one of my programs that I
needed, and couldn't figure a way around...
I mmap() files in, then copy them to a device. This works great except when
someone tries to change that file during the copy. If the size of the file
shrinks, I'll SIGBUS or SIGSEGV when i try to touch past the new file size.
So, i setup a signal handler and longjmp into some recovery code.
Perhaps there's a better way, but I don't consider this a bug really, and
i'll get a SEGV. :)
Kevin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
