Bug#343528: Acknowledgement (getmail4 crashes with segfault randomly when connecting to server [NOW WITH ATTACHMENT])

2005-12-17 Thread Rob Loos

Hi Fredrik,

Here soms answers:
1) the system is not using PAX currently, so no pax errors.
2) I ran against python 2.4.1, error remains
3) rebooted machine with sysctl tweakable kernel.
As the error seldom appears directly after a boot, I am currently unable 
to reproduce.

It may take weeks, but the error will return. Then I will report.

4) I'd like to try against python 2.4.2 because it fixes next possible 
related errors:
   - Patch #1297028: fix segfault if call type on MultibyteCodec, 
MultibyteStreamReader, or MultibyteStreamWriter.
   - Bug #110: The readline module could segfault if hook functions 
were set in a different thread than that which called readline.


But I can't because not available yet on sarge. Damn.

Rob


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#343527: getmail4 crashes with segfault randomly when connecting to server

2005-12-15 Thread Rob Loos

Package: getmail4
Version: 4.3.5
Debian: sarge

When I run getmail, after certain reboots it will constantly crash on 
some (not all) configuration files.
At some reboots the crashes occur immediately, at some reboots the 
crashes occur only after several days.


I added some basic info and some straces.
If needed, please specify the desired additional info.


Best Regards,

Rob Loos


---
$ getmail --rcfile configs/config1
/usr/lib/python2.3/optparse.py:668: FutureWarning: %u/%o/%x/%X of 
negative int will return a signed string in Python 2.4 and up

 return (%s at 0x%x: %r
getmail version 4.3.5
Copyright (C) 1998-2005 Charles Cazabon.  Licensed under the GNU GPL 
version 2.

SimpleIMAPSSLRetriever:[EMAIL PROTECTED]:993:
Segmentation fault

---
Python 2.3.5 (#2, Sep  4 2005, 22:01:42)
[GCC 3.3.5 (Debian 1:3.3.5-13)] on linux2



from kernel log:
grsec: From 192.168.1.102: denied resource overstep by requesting 4096 
for RLIMIT_CORE against limit 0 for /usr/bin/getmail[getmail:26500] 
uid/euid:1000/1000 gid/egid:1000/1000, parent /bin/bash[bash:30331] 
uid/euid:1000/1000 gid/egid:1000/1000


(remark, the cause is not a security feature of grsec ; grsec just 
reports the kernel error)



I added 3 configuration files: 2 with crash (1 imapSSL - config1, 1 
popSSL - config2), 1 working (popSSL - config3)

Then I added some straces of the crash.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]