acid tells us that we're indirecting a nil senders.last->p.
we know it's senders.last->p because it's at offset 4.
(that was the fault address.) the Lock at the beginning
of String is bigger than 4 bytes by itself, so it's not the
String and rsys is not the 2d pointer in NetConnInfo,
so that eli
Hello,
I added some debugging codes to catchalarm() in smtpd.c
static int
catchalarm(void *a, char *msg)
{
int rv = 1;
static int count = 0; // DEBUG by Kenar
count++;
if(count > 3)
return 0;
USED(a);
/* log alarms but continue */
if you look at /dev/kmesg you might find many messages about "checked N page
table entries".
i think smtpd is getting a trap (probably a null pointer) and because the value
returned
from catchalarm is the wrong way round, it continues to retry using the bad
pointer until
the alarm goes off (afte
> its not a good idea to call syslog() in a note handler, because it
> aquires locks
> and calls into the memory allocator by strdup() (that too aquires locks).
>
> if the note interrupts the program while in syslog() or the allocator,
> it will deadlock.
excellent point. in this case, i think
erik quanstrom wrote:
d'oh! the return value from catchalarm looks reversed. from notify(2)
[...] A handler must
return a non-zero number if the note was recognized (and
resolved); otherwise it must return zero. When the system
i think you're getting into some
d'oh! the return value from catchalarm looks reversed. from notify(2)
[...] A handler must
return a non-zero number if the note was recognized (and
resolved); otherwise it must return zero. When the system
i think you're getting into some sort of note loop. i t
Hello,
Today, I observed smtpd that was in endless loop and then broken.
ar% ps
...
none 203920:01 28:27 264K Running smtpd
...
ar% ACID 20392
/proc/20392/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: lstk()
receiver(path=0x41f58)+0x1c5 /sys/src/c
>> Is this phenomenon specific to me?
>
> No, it isn't:
>
> term% ps|grep Broken
> none9172:08 42:50 264K Broken smtpd
impressive!
i don't see this problem, but i have implemented
some fairly agressive spam control. perhaps this
shows up after i tend to hang up.
(it is
> Is this phenomenon specific to me?
No, it isn't:
term% ps|grep Broken
none9172:08 42:50 264K Broken smtpd
Hello,
I sometimes observe broken smtpd.
ar% ps
...
none19485780:01 44:55 264K Broken smtpd
none25211720:01 44:58 264K Broken smtpd
none31900370:01 45:03 264K Broken smtpd
...
ar% ACID 3190037
/proc/3190037/text:386 plan 9 executable
10 matches
Mail list logo
