Hi, For the record: The segmentation fault (which was reproducible) was fixed by upgrading perl module DBD::mysql from version 3.0000 to 3.0001. I can reboot the machine to be able to run PostMasterPOP3.pl again... I just hope there is no tidying up that needs to be done because a lock wasn't unlocked 'properly'... Regards, Rob. On 11/07/2005, at 9:41 AM, Rob Cas wrote:

Hi, I've been running 2.0.0b4 without problems (until today). On running PostMasterPOP3.pl the first 9 messages were retrieved correctly. Then a perl error followed by a segmentation fault (see below).

Now, if I try to run PostMasterPOP3.pl again, no messages are retrieved I get: Notice: PostMasterPOP3.pl is already running!

Has anybody seen this problem before and do you know: - if there is a lock file I need to remove to let me receive mail again? - what may have caused the crash in the first place?

Thanks in advance, Rob.

--- perl(453) malloc: *** error for object 0x1b26e00: incorrect checksum for freed object - object was probably modified after being freed, break at szone_error to debug perl(453) malloc: *** set a breakpoint in szone_error to debug

Message 10/28 (otrs@pop.someserver.com)

Message 11/28 (otrs@pop.someserver.com) Segmentation fault --- Thread 0 Crashed: 0 mysql.bundle 0x0061f888 escape_string_for_mysql + 396 (mysql.c:1946) 1 mysql.bundle 0x006172a8 mysql_real_escape_string + 20 (mysql.c:1946) 2 mysql.bundle 0x0060bbf4 mysql_st_internal_execute + 1284 (dbdimp.c:570) 3 mysql.bundle 0x00613aa4 XS_DBD__mysql__db_do + 2052 (mysql.xs:451) 4 DBI.bundle 0x00039cb0 XS_DBI_dispatch + 6384 (DBI.xs: 2658) 5 libperl.dylib 0x970b294c Perl_pp_entersub + 1292 6 libperl.dylib 0x970ab274 Perl_runops_standard + 64 7 libperl.dylib 0x970576fc S_run_body + 308 8 libperl.dylib 0x97057358 perl_run + 164