Ok, this together with the others is evidence that something runs really wild 
and overwrites memory blocks. The reason this message did not appear earlier is 
that I disable the check in DestroyMsg() and permit it to return even though I 
then know memory is corrupted. So what you see here is a follow-up error. 

The good news, I think, is that it looks (but may fool me) like the issue seems 
to be in temporal proximity of the abort. That would be really good news. Let 
me think a bit about the situation, I'll probably come up with another 
instrumentation. The issue is that I'd potentially need to output one or even 
two log lines per message, and that creates other sync issues. Plus, I don't 
know if I overrun your disk with that (depending on workload, which seems to be 
quite high).

Rainer

> -----Original Message-----
> From: [email protected] [mailto:rsyslog-
> [email protected]] On Behalf Of Lorenzo M. Catucci
> Sent: Friday, January 16, 2009 5:10 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] rsyslog still crashes
> 
> On Fri, 16 Jan 2009, Lorenzo M. Catucci wrote:
> 
> LMC>
> LMC> The -n crash was completely silent; the -d run was chatty (as
> expected);
> LMC> with stdout redirected, it took a lot more time to crash, but here
> are
> LMC> both the logfile and the gdb backtrace.
> LMC>
> 
> As for the last crash, I found on the screen session the line:
> 
> rsyslogd: queue.c:1393: queueChkDiscardMsg: Assertion `(unsigned)
> ((obj_t*)(pUsr))->iObjCooCKiE == (unsigned) 0xBADEFEE' failed.
> 
> since I forgot redirecting stderr too.
> 
> Yours,
> 
>       lorenzo
> 
> +-------------------------+--------------------------------------------
> --+
> |   Lorenzo M.  Catucci   | Centro di Calcolo e Documentazione
> |
> | [email protected] | Università degli Studi di Roma "Tor
> Vergata" |
> |                         | Via O. Raimondo 18 ** I-00173 ROMA  **
> ITALY |
> |  Tel. +39 06 7259 2255  | Fax. +39 06 7259 2125
> |
> +-------------------------+--------------------------------------------
> --+
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to