* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:> I attached gdb top a long running LMTP process: > > #0 sha1_loop (ctxt=0x7f3b1a4d7fa0, input=0x7f3b1a524860, len=0) at sha1.c:216 > input_c = 0x7f3b1a524860 "\211PNG\r\n\032\n" > gaplen = <optimized out> > gapstart = <optimized out> > off = 0 > copysiz = <optimized out> > > #1 0x00007f3b19195b29 in hash_format_loop (format=<optimized out>, data=0x7f3b1a524860, size=0) at hash-format.c:150 > list = 0x7f3b1a4d7f80It seems to loop in sha1_loop & hash_format_loop -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:> * Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > > I attached gdb top a long running LMTP process: > > > > #0 sha1_loop (ctxt=0x7f3b1a4d7fa0, input=0x7f3b1a524860, len=0) at sha1.c:216 > > input_c = 0x7f3b1a524860 "\211PNG\r\n\032\n" > > gaplen = <optimized out> > > gapstart = <optimized out> > > off = 0 > > copysiz = <optimized out> > > > > #1 0x00007f3b19195b29 in hash_format_loop (format=<optimized out>, data=0x7f3b1a524860, size=0) at hash-format.c:150 > > list = 0x7f3b1a4d7f80 > > It seems to loop in sha1_loop & hash_format_loopThe problem occurs in both 2.3 and 2.2 (I just updated to 2.3 to check). -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:> > It seems to loop in sha1_loop & hash_format_loop > > The problem occurs in both 2.3 and 2.2 (I just updated to 2.3 to check).I'm seeing the first occurence of that problem on the 10th of october! I was using (prior to the 10th) : 2.3.0~alpha0-1~auto+371 On the 10th I upgraded (16:04) to: 2.3.0~alpha0-1~auto+376 I'd think the change must have been introduced between 371 and 376 :) I then went back to, issues went away: 2.2.25-1~auto+49 and the issues reappeared with 2.2.25-1~auto+57 Does that help? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de