Re: still getting errors with CRM

   From: Paolo <[email protected]>

   On Wed, Apr 23, 2008 at 01:41:32PM +1000, Jason Lewis wrote:
   > question repeatedly, it happens between 2-6 times in 1000 classifications.

That's mighty perturbing.  Are you running out of process slots 
or memory?

Here's another hack to try:  At the VERY BOTTOM of mailreaver.crm
you will see a chunk of code that looks like this:

 #    Catch failures

 trap (:broken_program_message:) /.*/
 {
    accept
   
and then some OUTPUT statements.  Some of the output statements
have a 
   
  [stderr]

in them; others don't.

What you can do is to change all of the 

  [stderr] 

to 

  [ /tmp/crm114_errors.txt ]

and add that to the OUTPUT statements that don't have any [stderr] 
and then run your test loop.

The /tmp/crm114_errors.txt file should be most illuminating.... :-)


   > This is how I run it:
   > for i in {1..1000}; do crm -u . mailreaver.crm < 
   > sample-emails/1208918402.15894_1.debian\:2\,S | grep ERROR; done
   > 
   > Any ideas what I could do to get more info on why its crashing?

for-loops _should_ run sequentially. 
  

   (not so) wild guess: it's a 64bit issue. I'd rather not waste too
   much time on that, till the 'long* -> int*_t' conversion has been
   done.  Till then, you may want to try Gerrit's 'branch' which is
   supposed to track closely mainline on 'stable' classifiers and have
   a number of 64bit (possible) issues fixed.  Try that one, see if
   your loop (maybe go up to 10000) bombs out again.

Yes, try that too.

     - Bill Yerazunis

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone