[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [leafnode-list] Segfault on texpire

* Raymond Scholz wrote on Sat, Jun 15, 2002 at 08:14:47PM CEST:
> [...]
> fido.linux-ger: 0 articles deleted, 2 kept
> fido7.ru.palmtop: 0 articles deleted, 3 kept
> fido7.spb.palmpilot: 0 articles deleted, 3 kept
> Segmentation fault

Bad.  Nicely detailed log, thanks.  And AFAICS you're the third that's
reported this bug.

So a couple of questions to get a clue about what's happening, I have
yet to understand xgetxover: Since [1] is printed, texpire finished that
group.  What would be the next/current one?  What does it look like?
Group name with all numeric subpart?

If core file available: what are values of:

> 0x8052def in xgetxover (require_messageidlink=0, g=0x0) at xoverutil.c:495

xoverinfo, xoverinfo[0], xcount

> #0  0x8052def in xgetxover (require_messageidlink=0, g=0x0) at xoverutil.c:495
> #1  0x80527d7 in getxover (require_messageidlink=0) at xoverutil.c:304
> #2  0x804a984 in dogroup (g=0x401e3d74, expire=1021744950) at texpirec:782

*g describes the current group, that's where to look for possible trash
in .overview

> #3  0x804ac87 in expiregroup (g=0x4015d008) at texpire.c:883
> #4  0x804b17f in main (argc=1, argv=0xbffff9c4) at texpire.c:1058


leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list