Re: Cyrus debugging

2003-03-26 Thread Lawrence Greenfield
Date: Wed, 26 Mar 2003 09:17:02 -0500 From: Ken Murchison <[EMAIL PROTECTED]> [...] The majority of imapd's work is not done in imap* files. There are 80 LOG_DEBUG entries in the imap/ directory, and 141 in 2.1.12. This is in addition to all of the LOG_INFO, LOG_NOTICE, ... -- 990

Re: Cyrus debugging

2003-03-26 Thread Wayne Dawson
John Alton Tamplin wrote: When I want to debug an actual problem such as the core dump you refer to, I run the program under a debugger or at least investigate the core dump with a debugger. How does one run PHP code under a debugger? And how does one investigate a core dump with a debuger? Th

RE: Cyrus debugging

2003-03-26 Thread Oliver Pitzeier
John Alton Tamplin wrote: > Oliver Pitzeier wrote: > > Sorry, but I believe there are enough interessting parts in > > imapd and > > also in some lib/* file that could be logged for debugging reasons... > > Complaints about the code quality of Cyrus coming from > someone who tries to pass an i

Re: Cyrus debugging

2003-03-26 Thread Ken Murchison
John Alton Tamplin wrote: > > Oliver Pitzeier wrote: > > >Sorry, but I believe there are enough interessting parts in imapd and also in > >some lib/* file that could be logged for debugging reasons... > > > > > Complaints about the code quality of Cyrus coming from someone who tries > to pass a

Re: Cyrus debugging

2003-03-26 Thread John Alton Tamplin
Oliver Pitzeier wrote: Sorry, but I believe there are enough interessting parts in imapd and also in some lib/* file that could be logged for debugging reasons... Complaints about the code quality of Cyrus coming from someone who tries to pass an int where a char* is expected, whose patch resu

RE: Cyrus debugging

2003-03-26 Thread Oliver Pitzeier
Ken Murchison wrote: > The majority of imapd's work is not done in imap* files. > There are 80 LOG_DEBUG entries in the imap/ directory, and > 141 in 2.1.12. Sorry, but I believe there are enough interessting parts in imapd and also in some lib/* file that could be logged for debugging reasons.

Re: Cyrus debugging

2003-03-26 Thread Ken Murchison
Oliver Pitzeier wrote: > > Hi! > > The problem I'm currently working on shows me, that there is not a very good > error catching in Cyrus IMAP. There is a big difference between error catching and tracing execution with DEBUG messages. If you're trying to track down a crash, then you should b

Cyrus debugging

2003-03-26 Thread Oliver Pitzeier
Hi! The problem I'm currently working on shows me, that there is not a very good error catching in Cyrus IMAP. It also shows me, that there are too few debug possibilities. Look at this: [EMAIL PROTECTED] imap]$ grep -i debug imap* imapd.c:syslog(LOG_DEBUG, "open: user %s opened %s", imapd_us