Re: rare crash with

On Mon, Aug 1, 2011 at 2:53 PM, Rudy Gevaert <[email protected]> wrote:

> On 08/01/2011 12:45 PM, Bart Van Assche wrote:
>
>> Has this issue already been analyzed with Valgrind ?
>>
>
> I only ran gdb attached to the cyrus master daemon to get a backtrace.
> I haven't got any experience with valgrind, or debugging c code...
>

Using Valgrind isn't difficult. What you have to do is to type "valgrind" in
front of the name of the process you want to analyze. Also, the Valgrind
tool is since long included in every Linux distribution I know about. The
reason I'm asking this is because Valgrind is an excellent tool for
providing information about the cause of hard to reproduce software
problems. An example:

$ valgrind date
==2588== Memcheck, a memory error detector
==2588== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==2588== Using Valgrind-3.7.0.SVN and LibVEX; rerun with -h for copyright
info
==2588== Command: date
==2588==
Mon Aug  1 15:02:26 CEST 2011
==2588==
==2588== HEAP SUMMARY:
==2588==     in use at exit: 0 bytes in 0 blocks
==2588==   total heap usage: 11 allocs, 11 frees, 2,688 bytes allocated
==2588==
==2588== All heap blocks were freed -- no leaks are possible
==2588==
==2588== For counts of detected and suppressed errors, rerun with: -v
==2588== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)

Bart (who graduated from UGent).

------------------------------------------------------------------------------
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users