Package: pdnsd
Version: 1.2.2par-1
Severity: normal
pdnsd crashes when I put the system to sleep and wake it up (acpi S3),
when I strace it, or when I swsusp the system and restart it (which
works for me only with 2.6.13-rc3, but S3 works for me only with
2.6.11.4). I first noticed the problem with S3 and with swsusp, and
Pavel Machek suggested stracing to find out what goes wrong, and I was
surprised to find that strace alone crashes pdnsd.
With S3 sleep and wake, the message in the syslog is:
kernel: acpi_bus-0077 [51] acpi_bus_get_device : No context for object
[c15702c8]
pdnsd[3625]: Caught signal -1208217984. Exiting.
I can cause almost the same error by stracing pdsnd:
# strace -p `pidof pdnsd`
<lots of output beginning:>
Process 4496 attached - interrupt to quit
time(NULL) = 1122083668
write(3, "- 07/22 21:54:28| Signal -120821"..., 45) = 45
time(NULL) = 1122083668
write(3, "- 07/22 21:54:28| Writing cache "..., 64) = 64
<and ending:>
exit_group(0) = ?
Process 4496 detached
The pdnsd.debug log has
Signal -1208217984 caught
And the syslog has
pdnsd[4496]: Caught signal -1208217984. Exiting.
Looking at the source (main.c, line 652)
sigwait(&sigs_msk,&sig);
DEBUG_MSG("Signal %i caught.\n",sig);
I don't see how sig can get corrupted. sigwait is supposed to never
return an error. Is some bit of code not thread safe (enough)?
-Sanjoy
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.4-200503201
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages pdnsd depends on:
ii adduser 3.64 Add and remove users and groups
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
pdnsd recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
