[Top][All Lists]

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

Re: SIGSEGV, Segmentation fault.

From: Igor Homyakov
Subject: Re: SIGSEGV, Segmentation fault.
Date: Thu, 22 May 2003 11:03:27 +0400
User-agent: Mutt/1.4.1i

Ok. i have 2 linux servers. 

OS: ALT Linux Master 2.2 (

kernel-2.4.18-alt8-up (Xeon, 512Mb, IDE RAID)

kernel-2.4.20-alt5-smp (PIIx2, 512Mb, SCSI HDD)

monit from CVS builded on my desktop with gcc-3.2.1

When i run monit through valgrind (memory debuger) monit running
without SIGSERV.

$ sudo valgrind -v --leak-check=yes \
  ./monit -c /etc/monitrc >run.log 2>&1
$ sudo valgrind -v --leak-check=yes \
  ./monit -c /etc/monitrc validate >validate.log 2>&1
$ sudo valgrind -v --leak-check=yes \
  ./monit -c /etc/monitrc quit >quit.log 2>&1

** log attached ***

I also got SIGSEGV if running monit without gdb. 

Need you core dump ?

* Jan-Henrik Haukeland <hauk @ tildeslash . com> [030522 03:38]:
> Igor, it will help if you can tell us a bit more about the
> environment you have e.g. what kind of OS and glibc version 
> you are using and which version of monit you are running or 
> are you running the bleeding edge version from CVS? (I did 
> some changes to the log.c file in CVS lately)
> Even a copy of your monitrc control file would be nice.

> I have not seen this problem before, so I'm curious about 
> what and where the cause may be. (Well, it's almost certainly
> in the vsnprintf statement that builds the message buffer sent
> to syslog, this is also why syslog is mentioned in the 
> stack-trace from gbd. So, the response you got from Drepper 
> is probably correct, that is, the problem is most likely in the 
> monit code.

> But it's a strange problem because it must have turned up recently,
> if not you will have reported this earlier I guess. So, have 
> you done some strange things on your system lately, for instance 
> upgraded to RedHat 9.0? I have heard that they have a new thread 
> technology which are not backward compatible etc. Also a significant 
> question; do you also get SIGSEGV if you are *not* running monit 
> through the gdb debugger? 

> In other words all info you can provide may help :)

> Regards

> Jan-Henrik

> Ps. I'll be back on Friday and will give it a stab, if
> it's not already fixed by then by the other guys.

> --
> To unsubscribe:

Igor Homyakov
<homyakov AT>

Attachment: valgrind_monit_logs.tar.gz
Description: GNU Zip compressed data

reply via email to

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