Hi Suvayu,
you'll have to run valgrind on root.exe (yes, really, even on linux);
"root" (without ".exe") is a tiny wrapper that will not show any issues.
Cheers, Axel.
Suvayu Ali wrote on 10/06/2009 08:46 AM:
> Hi Rene,
>
> Sorry for the delay, I am on the west coast of Canada. :\
>
> On Sunday 04 October 2009 11:47 PM, Rene Brun wrote:
>> I cannot reproduce this problem.
>> Could you compile ROOT in debug mode, then run the valgrind
>> memory-checker on root.exe?
>>
> I have attached a file with all the particulars about the build
> environment and the options I used to build ROOT. It also includes the
> backtrace from the segfault. I have also attached the log file generated
> by valgrind. I used the following command to attach valgrind to root.
>
>> $ valgrind -v --log-file=valgrind-root.log root -l
>> MonitorESD_91890_1.root
>
> As reported earlier, after the segfault I had to kill ROOT with
> $ kill -9 <PID_for_root PID_for_root.exe>
>
> I also noticed that the segfault occurs only when I change something on
> the canvas using the histogram editor and try to close the TBrowser
> after saving it.
>
> I hope this will help you track things down. Hopefully its not some
> stupid mistake on my part :-p
>
> PS: If this makes any difference, the ROOT file was generated by ATHENA
> 15.4.0.1 (ROOT version 5.22). It is full of TH1Fs, TH2Fs and TProfiles.
>
> My system specifications:
> 2.6.30.8-64.fc11.x86_64
> ROOT 5.25/03
> g++ (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2)
>
>> Rene Brun
>
Received on Mon Oct 12 2009 - 11:21:38 CEST