- marked as minor
pilerimport - segmentation fault
Hi there,
I get a segmentation fault, after several minutes, when running pilerimport on a MailDir folder. Here is what strace generates:
It also segfaults when importing another mailbox via imap but this happens after several hours. Will try get a strace for it as well.
I am using 1.3.0.
kind regards
stat("./import/maildir/cur/1379449076.M666717P26777.anubis,S=3774,W=3866:2,S", {st_mode=S_IFREG|0600, st_size=3774, ...}) = 0
open("/dev/urandom", O_RDONLY) = 7
read(7, "\336KW\22\360", 5) = 5
close(7) = 0
unlink("400000005abf3cce2e4ac6d400de4b5712f0") = -1 ENOENT (No such file or directory)
unlink("400000005abf3cce2e4ac6d400de4b5712f0.m") = -1 ENOENT (No such file or directory)
stat("./import/maildir/cur/1379449076.M666717P26777.server1,S=3774,W=3866:2,S", {st_mode=S_IFREG|0600, st_size=3774, ...}) = 0
open("./import/maildir/cur/1379449076.M666717P26777.server1,S=3774,W=3866:2,S", O_RDONLY) = 7
open("400000005abf3cce2e4ac6d400de4b5712f0.m", O_RDWR|O_CREAT, 0600) = 9
fstat(7, {st_mode=S_IFREG|0600, st_size=3774, ...}) = 0
read(7, "Return-Path: <gg@designs."..., 4096) = 3774
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=271, ...}) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
Comments (10)
-
reporter -
reporter - edited description
-
repo owner The culprit might be an unclosed and thus leaking file descriptor in src/extract.c. Try the following: edit src/extract.c, and add the following:
There's the following code snippet at the end of the file:
wait(NULL); return; }
Fix it like this:
close(link[0]); wait(NULL); return; }
Then run make clean all in the src directory, stop piler, run make install, then start piler, and try the import again.
-
reporter Thanks for the feedback Janos. The line is already there. I am using 1.3.4 - sorry for the incorrect info above.
-
repo owner -
assigned issue to
-
assigned issue to
-
repo owner OK, no problem. Check if pilertest can process it. Btw, is ./import/maildir/cur/1379449076.M666717P26777.anubis,S=3774,W=3866:2,S the first file pilerimport would process or it has processed many files before reaching this file?
If nothing helps, this might be a parser error. In this case I'd like to see this file myself.
-
reporter I tried it with pilertest and it seg faults. Did a cat on the file and it looks ok. Will send you the file in a private message. Also this happens after the pilerimport has run for a while so it seems to just be this mail.
-
reporter Bit bucket doesn't appear to have a private messaging function :(
-
repo owner You may send it as a zip file to my address, see piler -V.
-
repo owner - changed status to closed
No news is good news.
- Log in to comment