From: Jakob Hirsch <jh@plonk.de>
To: mlmmj@mlmmj.org
Subject: Re: mlmmj-1.2.12-RC4 released
Date: Tue, 07 Nov 2006 09:36:48 +0000 [thread overview]
Message-ID: <455053B0.1020004@plonk.de> (raw)
In-Reply-To: <07000545535fd7f3f6fd56f93e19379f@mail.n0rd.dk>
Quoting Mads Martin Joergensen:
>>> Has anyone tested on exim, qmail or sendmail?
>> I wanted to test on Exim, but for some reason I could not figure out it
>> dumps core when I run
>> /usr/local/bin/mlmmj-recieve -L /var/spool/mlmmj/test -F <
>> mlmmj-coredump.msg
>> (message availabe at http://ymmv.de/sw/mlmmj/mlmmj-coredump.msg)
> And this is RC4 I assume?
Sure. RC1 runs fine, the RCs in-between I didn't test (but could if it
helps). Segfault is in mlmmj-process. I tried to debug it with gdb, but
it didn't like the core file (something like "unrecognized file
format"), and running it in gdb it says
(gdb) run -P -L /var/spool/mlmmj/test -m msg
Starting program: /usr/local/bin/mlmmj-process -P -L
/var/spool/mlmmj/test -m msg
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xc22000
Program received signal SIGSEGV, Segmentation fault.
0x0804cbf0 in myexcllock (fd=6) at mylocking.c:36
36 locktype.l_whence = SEEK_SET;
, which doesn't make sense to me (and is not correct, I think).
next prev parent reply other threads:[~2006-11-07 9:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 21:12 mlmmj-1.2.12-RC4 released Morten K. Poulsen
2006-10-02 16:04 ` Morten K. Poulsen
2006-10-11 8:58 ` Nico Meijer
2006-10-12 19:17 ` Morten K. Poulsen
2006-10-13 5:09 ` Nico Meijer
2006-11-06 20:11 ` Morten K. Poulsen
2006-11-07 0:33 ` Jakob Hirsch
2006-11-07 2:44 ` Mads Martin Joergensen
2006-11-07 9:36 ` Jakob Hirsch [this message]
2006-11-07 21:56 ` Morten K. Poulsen
2006-11-07 23:37 ` Jakob Hirsch
2006-11-08 18:27 ` Morten K. Poulsen
2006-11-09 8:14 ` Mads Martin Joergensen
2006-11-09 21:10 ` Morten K. Poulsen
2006-11-09 21:13 ` Andrea Barisani
2006-11-09 21:19 ` Morten K. Poulsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=455053B0.1020004@plonk.de \
--to=jh@plonk.de \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.