Your message dated Sun, 24 Dec 2017 08:57:46 +0900 with message-id <[email protected]> has caused the report #716252, regarding maildrop: reformime: null pointer dereference in extract_section() to be marked as having been forwarded to the upstream software author(s) [email protected]
(NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 716252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716252 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Hi, I just uploaded maildrop 2.9.3 to Debian. Thanks for many upstream fixes. I'm forwarding another bug report from the Debian bug tracking system (If you already dealt with this, sorry, missed it the last time around): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716252 --- From: Jakub Wilk <[email protected]> To: [email protected] Subject: Re: Bug#716252: [Mayhem] Bug report on courier-maildrop: reformime crashes with exit status 139 Date: Thu, 5 Oct 2017 18:12:44 +0200 Minimal reproducer: $ reformime -x -s moo < /dev/null Segmentation fault GDB says it's a null pointer dereference: Program received signal SIGSEGV, Segmentation fault. extract_section (top_rfcp=0x0, mimesection=0x565749b8 "moo", extract_filename=0x0, argc=0, argv=0xffffd584, extract_func=0x565587d0 <extract_file>) at reformime.c:656 656 if (top_rfcp->firstpart) (gdb) print top_rfcp $1 = (struct rfc2045 *) 0x0 (gdb) bt #0 extract_section (top_rfcp=0x0, mimesection=0x565749b8 "moo", extract_filename=0x0, argc=0, argv=0xffffd584, extract_func=0x565587d0 <extract_file>) at reformime.c:656 #1 0x56556ee5 in main2 (argv=<optimized out>, argc=<optimized out>, mimecharset=<optimized out>) at reformime.c:1181 #2 main (argc=<optimized out>, argv=<optimized out>) at reformime.c:1226 -- Jakub Wilk --- I still see the problem in 2.9.3 Regards, Osamu
--- End Message ---
