Hi, I did some more tracing. The last traced item before the SegV is the decoded commandtype as 1. I tried to figure out if it was crashing freeing the old username, but that wasn't the case (in fact username was always NULL in my crashes.) It then allocates a new username and goes out of pop3() and back into the read loop. It never gets to call pop3() with the PASS command. I was trying to take out the child signal handler to force it to create a core for debugging, but I was unable to do that. How can one do that? I can easily recreate the situation, but can't do it inside of gdb?! Thanks, Andy
On 12/10/02 5:24, "Roel Rozendaal - IC&S" <[EMAIL PROTECTED]> wrote: > Hi andreas, > > Your first problem has been fixed - cvs has been updated, i'll update > the 1.0 release today. The 2nd and 3rd problem you describe are > currently being looked into but all the information you (or anyone else > on this list) can send is very welcome. For instance, could you be more > specific on which commands are failing? Thanks! > > regards roel > > > Andreas Richter heeft op maandag, 9 dec 2002 om 12:49 > (Europe/Amsterdam) het volgende geschreven: > >> Hi, >> I am having problems with the 1.0 version. >> 1. IMAPD takes up all of the CPU after a while of being used. >> 2. POP3D crashes quite often and I had to revert to the rc4 version. >> 3. IMAPD sometimes doesn't let my client retrieve messages I get weird >> errors in the client saying that commands are invalid or the like, but >> the >> next retrieve works fine. >> I don't have any problems debugging this stuff, but I was unable to >> run the >> processes under gdb and would like some info on how to do that. >> Thanks, >> Andy >> >> _______________________________________________ >> Dbmail mailing list >> Dbmail@dbmail.org >> https://mailman.fastxs.nl/mailman/listinfo/dbmail > > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail > >
