unrtf segmentation fault

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

unrtf segmentation fault

Marco Spiga-2
OS OpenBSD 4.9 upgraded from 4.8

Command 'unrtf file.rtf' give me segmentation fault.
File seem regular because it can be converted on linux.

Reply | Threaded
Open this post in threaded view
|

Re: unrtf segmentation fault

Jasper Lievisse Adriaanse-2
On Thu, Jun 09, 2011 at 06:17:28PM +0200, [hidden email] wrote:
> OS OpenBSD 4.9 upgraded from 4.8
>
> Command 'unrtf file.rtf' give me segmentation fault.
> File seem regular because it can be converted on linux.

Are you kidding? How is this a useful report? There's no mention of which
platform you're using, or a backtrace or anything. You expect us to fix this
for you? Besides, ports issues are dealt with on ports@, not bugs@.

--
Cheers,
Jasper

"Capable, generous men do not create victims, they nurture them."

Reply | Threaded
Open this post in threaded view
|

Re: unrtf segmentation fault

Stuart Henderson
In reply to this post by Marco Spiga-2
On 2011/06/09 18:17, [hidden email] wrote:
> OS OpenBSD 4.9 upgraded from 4.8
>
> Command 'unrtf file.rtf' give me segmentation fault.
> File seem regular because it can be converted on linux.
>

OpenBSD's malloc picks up a lot of application bugs that wouldn't
be noticed on other OS without specialist debugging tools.

http://www.openbsd.org/papers/eurobsdcon2009/otto-malloc.pdf
http://www.undeadly.org/cgi?action=article&sid=20080708155228
http://en.wikipedia.org/wiki/Malloc#OpenBSD.27s_malloc

This does mean that you'll see more segfaults with buggy software,
but that means you get a better chance to debug them and get the
problem fixed, rather than have something silently proceed even
though there's a bug (only to have it intermittently fail in hard
to diagnose ways).

In general if you have segfaults you'll either need to provide
a backtrace, or provide a way to repeat it (this definitely
doesn't happen on every file with unrtf). But in this case
the version of unrtf in ports is ancient so there's no
point digging into it, I'll look at updating it, then if it
still fails with the new one you'll need to provide either
the file or a backtrace.

Please honour Reply-To: which is set to ports@.