Le message d'insulte: *** Break *** segmentation violation
=========================================================== There was a crash (#6 0xb72130fb in SigHandler(ESignals) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so). This is the entire stack trace of all threads: =========================================================== #0 0xb777c424 in __kernel_vsyscall () #1 0x43351fb3 in __waitpid_nocancel () from /lib/libc.so.6 #2 0x432d8a98 in do_system () from /lib/libc.so.6 #3 0xb720b22b in TUnixSystem::Exec(char const*) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #4 0xb7210421 in TUnixSystem::StackTrace() () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #5 0xb7212fe7 in TUnixSystem::DispatchSignals(ESignals) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #6 0xb72130fb in SigHandler(ESignals) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #7 0xb7209c32 in sighandler(int) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #8 0xb723bcd5 in textinput::TerminalConfigUnix::HandleSignal(int) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #9 0xb723bd14 in (anonymous namespace)::TerminalConfigUnix__handleSignal(int) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #10 <signal handler called> #11 0xb38a52e2 in KVIDGraph::GetName (this=0xbced140) at idmaps/KVIDGraph.cpp:1206 #12 0xb71513f9 in TNamed::ls(char const*) const () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #13 0xb71b1693 in TCollection::ls(char const*) const () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #14 0xb73cd8b2 in G__G__Base2_10_0_42(G__value*, char const*, G__param*, int) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #15 0xb6ab83ae in Cint::G__ExceptionWrapper(int (*)(G__value*, char const*, G__param*, int), G__value*, char*, G__param*, int) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCint.so #16 0xb6ab9eec in G__execute_call () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCint.so #17 0xb6aba2ea in G__call_cppfunc () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCint.so #18 0xb6b36afb in G__interpret_func () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCint.so #19 0xb6b79294 in G__getfunction () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCint.so #20 0xb6a92e67 in G__getstructmem(int, G__FastAllocString&, char*, int, char*, int*, G__var_array*, int) () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCint.so #21 0xbfc653c8 in ?? () =========================================================== The lines below might hint at the cause of the crash. If they do not help you then please submit a bug report at http://root.cern.ch/bugs. Please post the ENTIRE stack trace from above as an attachment in addition to anything else that might help us fixing this issue. =========================================================== #11 0xb38a52e2 in KVIDGraph::GetName (this=0xbced140) at idmaps/KVIDGraph.cpp:1206 #12 0xb71513f9 in TNamed::ls(char const*) const () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so #13 0xb71b1693 in TCollection::ls(char const*) const () from /home/dijon/.MyAppl/ROOT_CERN/.root-v5.34_gcc-4.7.2/lib/libCore.so =========================================================== -- You received this bug notification because you are a member of KaliVeda Development Team, which is subscribed to KaliVeda. https://bugs.launchpad.net/bugs/1469231 Title: segmentation violation lorsque l'on met une ChIo dans le fichier OoODetector.dat Status in KaliVeda data analysis framework: New Status in KaliVeda 1.10 series: New Bug description: lorsque l'on met chio (e.g CI_1202) dans le fichier OoODetectors.dat et que l'on appelle la methode gMultiDetArray->SetParameters(527) il y a une "segmentation violation". Le problème intervient lorsque l'on change deux fois le status fIsDetecting d'une KVChIo, ex: root [3] chio = gIndra->GetDetector("CI_0401") root [4] chio->SetDetecting(kFALSE) root [5] chio->SetDetecting(kTRUE) Lorsque la méthode gMultiDetArray->SetParameters(527) est appellée, KVDetector::SetDetecting est également appelée deux fois: une première fois dans KVINDRAUpDater::CheckStatusOfDetectors puis dans KVINDRAUpDater::SetChIoPressures To manage notifications about this bug go to: https://bugs.launchpad.net/kaliveda/+bug/1469231/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~kaliveda-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~kaliveda-dev More help : https://help.launchpad.net/ListHelp
