Bug#408531: glibc detected *** free(): invalid next size (fast): 0x ...

2007-02-02 Thread martin f krafft
also sprach Santiago Vila <[EMAIL PROTECTED]> [2007.02.02.1246 +0100]: > I don't think it is ok to submit a "severity: important" bug and > then not provide enough information to reproduce it. I just cannot reproduce it, and at the time I wrote the bug, my primary concern was getting my mail worki

Bug#408531: glibc detected *** free(): invalid next size (fast): 0x ...

2007-02-02 Thread Santiago Vila
severity 408531 normal tags 408531 + unreproducible thanks I don't think it is ok to submit a "severity: important" bug and then not provide enough information to reproduce it. At the very minimum, you should have done something like this: adduser somebody cp /home/madduck/.procmailrc /home/some

Bug#408531: glibc detected *** free(): invalid next size (fast): 0x ...

2007-01-28 Thread Santiago Vila
> > By "more specific" I mean a *complete* .procmailrc file and > > a *complete* message with which you can reproduce the error in > > this way: > > > > cat message | procmail > > > > Try to make both .procmailrc and the message the minimal ones with > > which you can reproduce it. > > I have no

Bug#408531: glibc detected *** free(): invalid next size (fast): 0x ...

2007-01-28 Thread martin f krafft
also sprach Santiago Vila <[EMAIL PROTECTED]> [2007.01.26.1522 +]: > May I ask you to be more specific? Of course, sorry. > By "more specific" I mean a *complete* .procmailrc file and > a *complete* message with which you can reproduce the error in > this way: > > cat message | procmail > >

Bug#408531: glibc detected *** free(): invalid next size (fast): 0x ...

2007-01-26 Thread Santiago Vila
On Fri, 26 Jan 2007, martin f krafft wrote: > Package: procmail > Version: 3.22-16 > Severity: important > > Accidentally, I put the following rule in place: > > :0 > : ^Delivered-To: [EMAIL PROTECTED] > > > (note the colon). > > This resulted in thousands of entries of > > procmail: Skipped

Bug#408531: glibc detected *** free(): invalid next size (fast): 0x ...

2007-01-26 Thread martin f krafft
Package: procmail Version: 3.22-16 Severity: important Accidentally, I put the following rule in place: :0 : ^Delivered-To: [EMAIL PROTECTED] (note the colon). This resulted in thousands of entries of procmail: Skipped "^Delivered-To: [EMAIL PROTECTED]" *** glibc detected *** free(): invalid