control: forcemerge -1 871266

Hi,

Just merging both reports since you didn't answered in #871266 and I'm
getting the same message on this one.

On Sat, Sep 02, 2017 at 09:20:50AM +0200, c.bu...@posteo.jp wrote:
> Here is the file causing the problem in the parser

That's what I get when trying to read your attachment under gdb with
--debug enabled:

tnef_parse.c:295:Tnef parser parsing part (42402).
tnef_parse.c:297:content: /home/mones/.claws-mail/mimetmp/claws.M95M9Y
Attempting to parse /home/mones/.claws-mail/mimetmp/claws.M95M9Y...
suspecting a corrupt file in UTF8 conversion
[Inferior 1 (process 11901) exited with code 0377]
(gdb) thread apply all bt
(gdb) bt all
No stack.
(gdb)

This message about corrupt file is printed by libytnef¹, which exits
without mercy under certain condition, a condition that your attachment
seems to be triggering.

I'm not expert in shared libraries but I'd say that calling exit() is
not the best way of dealing with errors, since it leaves no chance for
the program using the library.

I'll reassing this to libytnef package, so it can be forwarded to
libytnef upstream. Maybe they can provide a fix for this.

thanks for reporting,

¹ http://sources.debian.net/src/libytnef/1.9.2-2/lib/ytnef.c/?hl=221#L221
-- 
  Ricardo Mones 
  ~
  Physics is like sex: sure, it may give some practical results, but 
  that's not why we do it.                            Richard Feynman

Attachment: signature.asc
Description: PGP signature

Reply via email to