monit-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: core dump on reload


From: Christian Hopp
Subject: Re: core dump on reload
Date: Tue, 17 Feb 2004 15:52:52 +0100 (CET)

On Tue, 17 Feb 2004, Jan-Henrik Haukeland wrote:

>
> Monit dumps core on "monit reload", The backtrace from the core file:
>
>
> (gdb) bt
> #0  0x080626b4 in yylex () at lex.yy.c:2889
> #1  0x0805e82c in yyparse () at /usr/share/bison/bison.simple:573
> #2  0x08060071 in parse (controlfile=0x807cea0 "/home/hauk/.monitrc")
>     at p.y:1249
> #3  0x0804f86e in do_reinit () at monitor.c:277
> #4  0x0804fd52 in do_default () at monitor.c:510
> #5  0x0804f9bc in do_action (args=0xbfffeac4) at monitor.c:347
> #6  0x0804f691 in main (argc=2, argv=0xbfffeac4) at monitor.c:115
> #7  0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
>
>
> To reproduce:
>
>  1) Start monit -Iv
>  2) In another console do: monit reload
>
> Since this is happens in the new code added to the lexer, do you think
> you can take a look at it Christian ?

I can not reproduce it... for me the following happens:

#0  0x40254cdc in nanosleep () from /lib/tls/libc.so.6
#1  0x40254b18 in sleep () from /lib/tls/libc.so.6
#2  0x080508a7 in do_default () at monitor.c:507
#3  0x080506f5 in do_action (args=0x402df110) at monitor.c:347
#4  0x0805021f in main (argc=-516, argv=0xbffffac4) at monitor.c:115

I don't even get to the lexer.  And my lexer produces diffentent code!

Christian

-- 
Christian Hopp                                email: address@hidden
Institut für Elektrische Informationstechnik             fon: +49-5323-72-2113
TU Clausthal, Leibnizstr. 28, 38678 Clausthal-Zellerf.   fax: +49-5323-72-3197
                             pgpkey: https://www.iei.tu-clausthal.de/pgp-keys/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]