← Back to team overview

kaliveda-dev team mailing list archive

  1. kaliveda-dev team
  2. Mailing list archive
  3. Message #00476

[Bug 918206] [NEW] segV with analyse_logs when GE has a "timeout"

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

Quand je lance un analyse_logs, tantôt cela fonctionne, tantôt ça se
plante. La commande que je donne est la même sinon que le nom générique
des runs est différent. Si je comprend bien le diagnostic, c'est le nom
qui est en cause, en tant que TString. Voici la réponse obtenue :

analyse_logs recon_ident_kv1.8.3_136Xe124Sn32

 *** Break *** segmentation violation


===========================================================
There was a crash.
This is the entire stack trace of all threads:
===========================================================
#0  0x00002aadf45ea115 in waitpid () from /lib64/libc.so.6
#1  0x00002aadf458c481 in do_system () from /lib64/libc.so.6
#2  0x00002aadeed4eb12 in TUnixSystem::StackTrace() ()
   from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
#3  0x00002aadeed4b9ca in TUnixSystem::DispatchSignals(ESignals) ()
   from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
#4  <signal handler called>
#5  0x00002aadeecb452c in TString::TString(TString const&) ()
   from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
#6  0x00002aadf3118207 in KVGELogReader::ReadMemUsed (this=0x7fffee9adf10, 
    line=...) at base/KVGELogReader.cpp:83
#7  0x00002aadf311867c in KVGELogReader::ReadLine (this=0x7fffee9adf10, 
    line=..., ok=
0x7fffee9add0f) at base/KVGELogReader.cpp:44
#8  0x00002aadf312603e in KVLogReader::ReadFile (this=0x7fffee9adf10, 
    fname=0xf61c9a0 "recon_ident_kv1.8.3_136Xe124Sn32_R7144.o4345429")
    at base/KVLogReader.cpp:45
#9  0x0000000000403be5 in main ()
===========================================================


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.
===========================================================
#5  0x00002aadeecb452c in TString::TString(TString const&) ()
   from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
#6  0x00002aadf3118207 in KVGELogReader::ReadMemUsed (this=0x7fffee9adf10, 
    line=...) at base/KVGELogReader.cpp:83
#7  0x00002aadf311867c in KVGELogReader::ReadLine (this=0x7fffee9adf10, 
    line=..., ok=
0x7fffee9add0f) at base/KVGELogReader.cpp:44
#8  0x00002aadf312603e in KVLogReader::ReadFile (this=0x7fffee9adf10, 
    fname=0xf61c9a0 "recon_ident_kv1.8.3_136Xe124Sn32_R7144.o4345429")
    at base/KVLogReader.cpp:45
#9  0x0000000000403be5 in main ()
===========================================================


Segmentation fault (core dumped)

   Quelqu'un d'autre a-t-il eu cet ennui ?

** Affects: kaliveda
     Importance: Medium
     Assignee: John Frankland (frankland)
         Status: In Progress

** Affects: kaliveda/1.8
     Importance: Medium
     Assignee: John Frankland (frankland)
         Status: In Progress

** Also affects: kaliveda/1.8
   Importance: Undecided
       Status: New

** Changed in: kaliveda/1.8
    Milestone: None => 1.8.4

** Changed in: kaliveda/1.8
   Importance: Undecided => Medium

** Changed in: kaliveda/1.8
     Assignee: (unassigned) => John Frankland (frankland)

** Changed in: kaliveda/1.8
       Status: New => In Progress

-- 
You received this bug notification because you are a member of KaliVeda
Development Team, which is subscribed to KaliVeda.
https://bugs.launchpad.net/bugs/918206

Title:
  segV with analyse_logs when GE has a "timeout"

Status in KaliVeda data analysis framework:
  In Progress
Status in KaliVeda 1.8 series:
  In Progress

Bug description:
  Quand je lance un analyse_logs, tantôt cela fonctionne, tantôt ça se
  plante. La commande que je donne est la même sinon que le nom
  générique des runs est différent. Si je comprend bien le diagnostic,
  c'est le nom qui est en cause, en tant que TString. Voici la réponse
  obtenue :

  analyse_logs recon_ident_kv1.8.3_136Xe124Sn32

   *** Break *** segmentation violation


  ===========================================================
  There was a crash.
  This is the entire stack trace of all threads:
  ===========================================================
  #0  0x00002aadf45ea115 in waitpid () from /lib64/libc.so.6
  #1  0x00002aadf458c481 in do_system () from /lib64/libc.so.6
  #2  0x00002aadeed4eb12 in TUnixSystem::StackTrace() ()
     from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
  #3  0x00002aadeed4b9ca in TUnixSystem::DispatchSignals(ESignals) ()
     from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
  #4  <signal handler called>
  #5  0x00002aadeecb452c in TString::TString(TString const&) ()
     from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
  #6  0x00002aadf3118207 in KVGELogReader::ReadMemUsed (this=0x7fffee9adf10, 
      line=...) at base/KVGELogReader.cpp:83
  #7  0x00002aadf311867c in KVGELogReader::ReadLine (this=0x7fffee9adf10, 
      line=..., ok=
  0x7fffee9add0f) at base/KVGELogReader.cpp:44
  #8  0x00002aadf312603e in KVLogReader::ReadFile (this=0x7fffee9adf10, 
      fname=0xf61c9a0 "recon_ident_kv1.8.3_136Xe124Sn32_R7144.o4345429")
      at base/KVLogReader.cpp:45
  #9  0x0000000000403be5 in main ()
  ===========================================================

  
  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.
  ===========================================================
  #5  0x00002aadeecb452c in TString::TString(TString const&) ()
     from /afs/in2p3.fr/throng/indra/.root-5.33_gcc-4.1.2_x86_64/lib/libCore.so
  #6  0x00002aadf3118207 in KVGELogReader::ReadMemUsed (this=0x7fffee9adf10, 
      line=...) at base/KVGELogReader.cpp:83
  #7  0x00002aadf311867c in KVGELogReader::ReadLine (this=0x7fffee9adf10, 
      line=..., ok=
  0x7fffee9add0f) at base/KVGELogReader.cpp:44
  #8  0x00002aadf312603e in KVLogReader::ReadFile (this=0x7fffee9adf10, 
      fname=0xf61c9a0 "recon_ident_kv1.8.3_136Xe124Sn32_R7144.o4345429")
      at base/KVLogReader.cpp:45
  #9  0x0000000000403be5 in main ()
  ===========================================================

  
  Segmentation fault (core dumped)

     Quelqu'un d'autre a-t-il eu cet ennui ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/kaliveda/+bug/918206/+subscriptions

Follow ups

References

  Thread Previous • Date Previous • • Thread Next