Your message dated Sat, 11 Jul 2015 13:20:43 +0200
with message-id <55a0fc0b.5000...@debian.org>
and subject line Re: Bug#690034: libmilter1.0.1: milters crash when under high
load
has caused the Debian Bug report #690034,
regarding libmilter1.0.1: milters crash when under high load
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(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 ow...@bugs.debian.org
immediately.)
--
690034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmilter1.0.1
Version: 8.14.4-2.1
Severity: normal
Hi,
I've got serveral milters when crash when under high load.
The problem seems to be that a signal is caught in poll but the handler doesn't
do the right thing.
I think the problem is that the signal shouldn't fire at all.
From the core I've got the following backtrace:
Program terminated with signal 6, Aborted.
#0 0x7f4bdfe01475 in *__GI_raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x7f4bdfe01475 in *__GI_raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x7f4bdfe046f0 in *__GI_abort () at abort.c:92
#2 0x7f4bdfe3b32b in __libc_message (do_abort=,
fmt=) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#3 0x7f4bdfebbf37 in *__GI___fortify_fail (msg=0x7f4bdff19c68 "longjmp
causes uninitialized stack frame") at fortify_fail.c:32
#4 0x7f4bdfebbec9 in longjmp_chk () at
../sysdeps/unix/sysv/linux/x86_64/longjmp_chk.S:86
#5 0x7f4bdfebbe33 in __longjmp_chk (env=env@entry=0x7f4be05d5c40,
val=val@entry=1) at ../setjmp/longjmp.c:40
#6 0x7f4be037dc85 in alarmfunc (sig=) at hostip.c:515
#7
#8 0x7f4bdfe9cac3 in *__GI___poll (fds=,
fds@entry=0x7fffe23cd280, nfds=, nfds@entry=1,
timeout=timeout@entry=5000)
at ../sysdeps/unix/sysv/linux/poll.c:87
#9 0x7f4be05de484 in mi_listener (conn=, dbg=0,
smfi=0x14b09f0, timeout=7210, backlog=) at listener.c:766
#10 0x7f4be05defd7 in smfi_main () at main.c:242
#11 0x00402621 in main (argc=5, argv=0x7fffe23cd508) at
disclaimermilter.c:560
Is there any more information I can add which will help?
Cheers,
Scott
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libmilter1.0.1 depends on:
ii libc6 2.13-35
libmilter1.0.1 recommends no packages.
libmilter1.0.1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2015-07-11 12:08, Scott Ashcroft wrote:
> This turned out to be a thread safety caused by another library I was
> linking with.
> Once I'd sorted that out I couldn't trigger the crash.
>
> Please close the bug.
Thanks for the feedback, closing.
Andreas--- End Message ---
