Analysis

Help: Forums, postings and threads

Forums, postings and threads

Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.

Layout of the posting thread(s)

The posting threads can be shown with/without the text of the postings ("Inline depth"). In addition the depth of the thread can be controlled ("Outline depth"). For both cases several values are provided, which can be toggled. Note that the displayed values are those, which can be chosen, they do not correspond to the actual display status of the thread(s).

Add message

Add a new posting thread to this Forum

Show subscribers

Click "Show subscribers" to get the List of all subscribers, who receive e-mail from postings to this Forum, if they have not explictly unsubscribed from a posting thread. This includes:

Subscribers to the forum
Explicit subscribers to the posting or any of its ancestors
The author of the posting (if he has not unsubscribed)
The authors of any ancestor posting (if they have not unsubscribed)

Some browsers display old pages from the cache

Some browsers (e.g. Firefox) display a page from the cache even though the page has been updated. As a result, one may not get the latest messages in the forum's outline or the logon ID of the previous session appears on the upper right corner. If one suspects that he or she does not get the latest content of a page, try clearing up the personal data from the browser's cache as the following:

Tools -> Clear Private Data -> Clear Private Data (from browser Firefox)

Tools -> Delete Private Data (from browser Opera)

then reflesh the current page to get the latest content.

Details on "Inline depth" and "Outline depth"

Threads and the follow-up messages are numbered. There is one line per posting, normally starting with the posting number. The URLs of a posting and its responses reflect the depth of the follow-up postings. Watch the URLs to see how this is done. Depending on the chosen display options, the thread-display may be incomplete; the number of messages at the next level is, however, displayed, e.g. "…3 message(s)". You may not see all contributors unless you choose "All".

Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.

Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.

Argument Default value Alternative Comment

1 0 1 no text / full text of posting

2 1 All text for level 1 only / text for All postings

Argument	Default value	Alternative		Comment
1	0	1		no text / full text of posting
2	1	All		text for level 1 only / text for All postings

Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.

Argument Default value Alternative Comment

1 2 1 2 levels / 1 level (original posting)

2 3 2 3 levels / 2 levels

3 3 All 3 levels / all levels (all postings)

The analysis forum discusses various analysis packages (histogramming, n-tuples, etc.) and their interfaces.

Argument	Default value	Alternative	Comment
1	2	1	2 levels / 1 level (original posting)
2	3	2	3 levels / 2 levels
3	3	All	3 levels / all levels (all postings)

GLIBC2.4 for OpenScientist or alternate solution for AIDA by Daniel Sánchez Parcerisa <Daniel Sánchez Parcerisa>, Nov 23, 12:30 Hello I am trying to fully install Geant4 but having problems with the AIDA functionality. I am trying to install OpenScientist as AIDA implementation, but it requires libraries GLIBC2.4, and my current SuSe distribution does not have them, so I get compilation / linkage errors. Anyone has come up with the same problem? Anyone knows how to safely update GLIBC and making it available for OpenScientist, or know if the other implementations not require so new libraries?

Re: GLIBC2.4 for OpenScientist or alternate solution for AIDA by Guy Barrand <Guy Barrand>, Nov 24, 00:18 Re: GLIBC2.4 for OpenScientist or alternate solution for AIDA (Daniel Sánchez Parcerisa) Hi "Standard question" : What is your g++ version ? (g++ --version). The best is to recompile. Few chance to be able to run with a glibc which is not binary compatible. One nasty point with glibc is that it is used in a shared way by... the UNIX commands ! So that if you attempt to have an incompatible glibc in your PATH (LD_LIBRARY_PATH), your are going to screw up your shell session. For G4 you need mainly to install a "osc_batch" kit (to save histos and tuples in files). This kind of kit does not need some graphics, mainly only g++. See my web pages to build from source. And tell me your g++ version (and in fact your SuSe version, I can perhaps get a virtual machine of it) (for VirtualBox it seems that I have OpenSUSE-10.0, 11.0, 11.1) Cheers. Guy

OnX::XtUI::LookDSM_Problem by David Gladstone <David Gladstone>, Nov 17, 06:57 I encountered this error when running a program compiled to use OpenScientist for visualization. The problem was resolved by changing the order in which environment variables are set. I set my system environment variables (Ubuntu 9.04) geant 4.9.2.p02 in the .tcshrc file as follows: source ~/geant4.9.2.p02/env.csh source /home/david/open_scientist/osc_vis/16.8/setup.csh setenv PATH "/home/david/xerces-c-3.0.1-x86_64-linux-gcc-3.4/bin":$PATH setenv PATH "/opt/ActiveTcl-8.5/bin":$PATH setenv G4WORKDIR /home/david/g4work The OnX problem occurred when the env.csh and setup.csh (first two lines) were at the end of the .tcshrc file. The problem went away when they are listed as shown above. So, if you get this error, try changing the order in which you load your environment variable or path settings. David

Re: OnX::XtUI::LookDSM_Problem by Guy Barrand <Guy Barrand>, Nov 17, 08:09 Re: OnX::XtUI::LookDSM_Problem (David Gladstone) Hi The "DSM problem" is something that happens if you finish to have in a program, in the link command the Xt toolkit coming before Motif, that is to say link with : -lXt -lXm instead of : -lXm -lXt. Then the XtInitialize simply stops with some strange message "DSM problem" ! I have finished to understand what is behind this (strange) message and in OnX/Xt I try to bypass that. But it seems that you fall on some new strange situation. Due to the "multi driver" way of Geant4, then Xt, Xm may come from different channels and then you may finish to be in this situation. Could be fine to check what you get at link time for you particular case... But not clear to my why reversing some path in the PATH permits you to pass... Cheers Guy

I can't open hadrontherapy.root files by using JAS3 by Jongseok <Jongseok>, Nov 08, 23:02 Hi! I was trying to make output files for many examples. Eventually I succeeded to make output files for Brachytherapy, AnaEx01, and hadrontherapy, because many users in this Forum helped me. Unfortunately, I faced other problem that I can't open my output files. I can open output files(.root and .aida) for brachytherapy and anaex01 through JAS3 program, but I can't open only hadrontherapy.root file. JAS3 program showed me that some errors are occurred during command processing. I also update my JAS3 program to 0.8.4. How can I solve this problem? Please give me some advice. Thanks. Jongseok.

How can I make output file for Hadrontheraphy?? by Jongseok <Jongseok>, Oct 25, 00:46 Hi everyone. I'm struggling with making an output file for the hadrontherapy example. I already read the README file, so I declared G4ANAYLISYS_USE as 1. (export G4ANALYSIS_USE=1 or declared variable in hadrontherapy.cc) Also, I copied AIDA header files in subdirectory of hadrontherapy example (~/AIDA). But I couldn't make *.hbk output file... I have used Hadrontherapy example by using VisualizationMacro file. In order to make output file, What should I do more? Please give some advice.. Thanks. Compapaa

Re: How can I make output file for Hadrontheraphy?? by G.A.P.Cirrone <G.A.P.Cirrone>, Oct 25, 14:54 Re: How can I make output file for Hadrontheraphy?? (Jongseok) Dear User, in the actual public version of Hadrontherapy (included in the 9.2 geant4 distribution) .root (and eventually .xml files) can be generated is a correct version of one of the AIDA implementation is correctly installed on your computer. AIDA is a collection of libraries permmiting you to generate output file. By the Way it is not necessary and directly the ROOT libraries can be called (if you have ROOT installed in your machine). We created a small guide to install AIDA in a Linux OS. It is yet in Italian but I think you can easily follow the steps. The guide is at: http://workgroup.lngs.infn.it/geant4lns/GROUP%20DISCUSSIONS%20FOLDER/aida-installation-manual/at_download/file Moreover, please try to read the other posts on the argument. I.E.: http://hypernews.slac.stanford.edu/HyperNews/geant4/get/medical_app/202.html or others If you want you can also generate simple ASCII file of the dose matrix in hadrontherapy. I provided this functionality in the actual Beta version of Geant4. If you are interested in this please, download the Geant4 Beta version, go in the Hadrontherapy folder and copy only the HadrontherapyMatrix.cc Class file. Then recompile. Now .out text file are generated without the use of the AIDA interface or other external libraries. Cheers Pablo CirroneOn Sun, 25 Oct 2009 07:46:28 GMT, Jongseok wrote: > Hi everyone. > > I'm struggling with making an output file for the hadrontherapy example. > > I already read the README file, so I declared G4ANAYLISYS_USE as 1. > > (export G4ANALYSIS_USE=1 or declared variable in hadrontherapy.cc) > > Also, I copied AIDA header files in subdirectory of hadrontherapy > example > > (~/AIDA). > > But I couldn't make *.hbk output file... > > I have used Hadrontherapy example by using VisualizationMacro file. > > In order to make output file, What should I do more? > > Please give some advice.. > > Thanks. > > Compapaa >

Re: How can I make output file for Hadrontheraphy?? by Jongseok <Jongseok>, Oct 26, 04:37 Re: Re: How can I make output file for Hadrontheraphy?? (G.A.P.Cirrone) Dear Pablo CirroneOn. I really appreciate to answer my question!! As you said, I downloaded OpenScientist(version 16.9), and I finished installation without any error message. I also declared G4ANALYSIS_USE as 1, and confirm that AIDA is correctly installed by typing aida-config. I saw the same message in the aida setup manual that you gave me. However, I couldn't get *.hbk output file. I'm really sorry that I have to ask again. Please help me!! Thanks. Compapa

Re: How can I make output file for Hadrontheraphy?? by michel maire <michel maire>, Oct 26, 06:39 Re: Re: How can I make output file for Hadrontheraphy?? (Jongseok) > > As you said, I downloaded OpenScientist(version 16.9), and I finished > > installation without any error message. > > > However, I couldn't get *.hbk output file. I'm really sorry that I have > to ask I guess .hbk is not a valid extension for aida/openScientist. Use .hbook instead (See also examples/extended/electromagnetic/TestEm1 : README and installAida.txt)

Analysis with Geant4,cygwin,MVS.Net,JAIDA-3.2.1,AIDAJNI-3.2.0 by Elin Aronsen <Elin Aronsen>, Sep 21, 18:14 I have a problem in running Geant4.8.2.p01 on Windows XP with cygwin, MVS .NET 2003, JAVA, JAIDA and AIDAJNI. The plan is to take 1Dhistogram files created when running the extended example with added selected trajectories in TrackingAction.cc into JAS3 for further adding of several histograms (from many runs). But the problem arrived that the program created only the HistoManager.o file (may be when booking at the begin of the run), but I never located any hbook uncompressed file containing the necessary histogram. The program runs without error messages and without creating the wanted file. It seems that the program is filling the histogram all right in the TrackingAction.cc file as I get written out from there indicating that the histogram ID (exist(ID) has the boolean value true).But then nothing more happens. Further I did not manage to set the directory histoDir using command /testem/histo/ as given in the HistoMessenger.cc file. The guidance did not help me and there was no feedback when trying to give some directory path. I am not sure if it should be necessary to set the directory since no .mac file and no example is actually setting the directory in the TestEm3 or any other example. I hope that you can help me. May be that also some lines in the Histomanager.cc file could set the directory.I am using the extended example TestEm3 mostly with only selected as trajectories those being reflected from the metal sheet. Thanks. Elin Aronsen Attachment:Output9.17se,TrackingAction.cc,TestEm3.cc,RunAction.cc,EventAction.cc http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/09/21/17.57-85182-9.17TrackingAction.cc http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/09/21/17.57-55727-9.17HistoManager.cc http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/09/21/17.57-48473-9.17TestEm3.cc http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/09/21/17.57-65871-9.17RunAction.cc http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/09/21/17.57-11264-9.17EventAction.cc

AIDA&AIDAJNI Problems by <Nathan.C.Nelson@Hitchcock.org>, Sep 09, 10:27 Hi, I am a recent user of GEANT4. I have the latest version of GEANT4 (4.9.p02)installed on our Ubuntu 9.04 platform along with Sun Java 1.6, AIDAJNI 3.2.6 and JAIDA 3.2.4. I can compile and run examples such as N01, A01 etc but when turning on analysis I get many linking errors for A01 similar to other posted users. I have noticed that I can get the AIDAJNI example AidaTest to work if I add my shared library /usr/lib/libstdc++.so.5 to link up. If I use the default shared library /usr/lib/libstdc++.so.6 on my system I get the same linking errors as above. If I add /usr/lib/libstdc++.so.5 in the GNUmakefile of example A01 it links with no errors but when I execute A01app I get a segmentation fault. I'm not sure if I can re-compile GEANT4 using libstdc++.so.5 if that would solve the problem?? (I don't know how to force Ubuntu 9.04 to use libstdc++.so.5 instead of libstdc++.so.6! I appreciate any help in this matter out there in GEANT4 land...

histogram parameters by Lorena Magallanes <Lorena Magallanes>, Sep 02, 06:46 Hi, I´m working with examples like TestEm* but It is necessary to me get a histogram in MeV/mm3 instead of MeV/mm, How can I change these unit? Thanks in advance. L. Magallanes

Problem running example A01 and N02 by Neoh <Neoh>, Jul 17, 12:05

Hi,
I have geant4.9.2.p01 in my Debian GNU/Linux. I tried to install Open Scientist as AIDA implementation of my Geant4 toolkit. To test my AIDA installation, I followed instructions on its homepage to create a cpp file, compile and run it with output " :-) AIDA found." as expected, so I assumed the AIDA installation is successful at this point(hopefuly).
The problem comes when I tried to test-run example A01. I source both env.sh from geant4 installation directory and aida-setup.sh from osc_vis,unset the variables G4VIS_BUILD_OPENGLX_DRIVER, G4VIS_BUILD_OPENGLXM_DRIVER and G4LIB_USE_GRANULAR, then type "make".This is the output:
Making dependency for file A01app.cc ... Making dependency for file src/A01Trajectory.cc ... Making dependency for file src/A01PrimaryGeneratorMessenger.cc ... Making dependency for file src/A01PrimaryGeneratorAction.cc ... Making dependency for file src/A01PhysicsList.cc ... Making dependency for file src/A01MuonPhysics.cc ... Making dependency for file src/A01MagneticFieldMessenger.cc ... Making dependency for file src/A01MagneticField.cc ... Making dependency for file src/A01IonPhysics.cc ... Making dependency for file src/A01HodoscopeHit.cc ... Making dependency for file src/A01Hodoscope.cc ... Making dependency for file src/A01HadronPhysics.cc ... Making dependency for file src/A01HadCalorimeterHit.cc ... Making dependency for file src/A01HadCalorimeter.cc ... Making dependency for file src/A01GeneralPhysics.cc ... Making dependency for file src/A01EventActionMessenger.cc ... Making dependency for file src/A01EventAction.cc ... Making dependency for file src/A01EMPhysics.cc ... Making dependency for file src/A01EmCalorimeterHit.cc ... Making dependency for file src/A01EmCalorimeter.cc ... Making dependency for file src/A01DriftChamberHit.cc ... Making dependency for file src/A01DriftChamber.cc ... Making dependency for file src/A01DetectorConstruction.cc ... Making dependency for file src/A01DetectorConstMessenger.cc ... Making dependency for file src/A01CellParameterisation.cc ... Making dependency for file src/A01AnalysisManager.cc ... Compiling A01AnalysisManager.cc ... In file included from src/A01AnalysisManager.cc:60: include/A01AnalysisManager.hh:56: warning: declaration ‘class AIDA::IAnalysisFactory’ does not declare anything include/A01AnalysisManager.hh:57: warning: declaration ‘class AIDA::ITree’ does not declare anything include/A01AnalysisManager.hh:58: warning: declaration ‘class AIDA::IHistogramFactory’ does not declare anything include/A01AnalysisManager.hh:59: warning: declaration ‘class AIDA::ITupleFactory’ does not declare anything include/A01AnalysisManager.hh:60: warning: declaration ‘class AIDA::IPlotter’ does not declare anything Compiling A01CellParameterisation.cc ... Compiling A01DetectorConstMessenger.cc ... Compiling A01DetectorConstruction.cc ... Compiling A01DriftChamber.cc ... Compiling A01DriftChamberHit.cc ... Compiling A01EmCalorimeter.cc ... Compiling A01EmCalorimeterHit.cc ... Compiling A01EMPhysics.cc ... Compiling A01EventAction.cc ... In file included from src/A01EventAction.cc:33: include/A01AnalysisManager.hh:56: warning: declaration ‘class AIDA::IAnalysisFactory’ does not declare anything include/A01AnalysisManager.hh:57: warning: declaration ‘class AIDA::ITree’ does not declare anything include/A01AnalysisManager.hh:58: warning: declaration ‘class AIDA::IHistogramFactory’ does not declare anything include/A01AnalysisManager.hh:59: warning: declaration ‘class AIDA::ITupleFactory’ does not declare anything include/A01AnalysisManager.hh:60: warning: declaration ‘class AIDA::IPlotter’ does not declare anything Compiling A01EventActionMessenger.cc ... Compiling A01GeneralPhysics.cc ... Compiling A01HadCalorimeter.cc ... Compiling A01HadCalorimeterHit.cc ... Compiling A01HadronPhysics.cc without optimization... Compiling A01Hodoscope.cc ... Compiling A01HodoscopeHit.cc ... Compiling A01IonPhysics.cc ... Compiling A01MagneticField.cc ... Compiling A01MagneticFieldMessenger.cc ... Compiling A01MuonPhysics.cc ... Compiling A01PhysicsList.cc ... Compiling A01PrimaryGeneratorAction.cc ... Compiling A01PrimaryGeneratorMessenger.cc ... Compiling A01Trajectory.cc ... Creating shared library /root/geant4/tmp/Linux-g++/A01app/libA01app.so ... /usr/bin/ld: cannot find -lG4readout collect2: ld returned 1 exit status make: *** [/root/geant4/tmp/Linux-g++/A01app/libA01app.so] Error 1
When I tried to run example N02, it gives the same error: . . . Creating shared library /root/geant4/tmp/Linux-g++/exampleN02/libexampleN02.so ... /usr/bin/ld: cannot find -lG4readout collect2: ld returned 1 exit status make: *** [/root/geant4/tmp/Linux-g++/exampleN02/libexampleN02.so] Error 1
Does anyone have any idea what is the problem? I tried to compile example N01 but it didn't show any error.
Regards,
Neoh

Replica and energy density deposition by Olivier Dadoun <Olivier Dadoun>, Jul 07, 03:02 Hello, I am studying the energy density deposition (unit in MeV/mm3) inside a Target of Tungsten. To do so I have segmented my target in N_Cell_z*N_Cell_x*N_Cell_y which are my elementary volumes (using Replica Volume). I retrieved the cell hits using G4int NrX = aStep->GetPreStepPoint()->GetTouchable()->GetReplicaNumber(1); G4int NrY = aStep->GetPreStepPoint()->GetTouchable()->GetReplicaNumber(2); G4int NrZ = aStep->GetPreStepPoint()->GetTouchable()->GetReplicaNumber(0); and the cumulated deposited energy is depESum[NrZ][NrX][NrY] += aStep->GetTotalEnergyDeposit(); Finally I fill a 3D histo using ROOT. I am interested in the Peak Energy Density Deposition, i.e the maximum value of depESum divided by the volume of the elementary cell volume. My problem is that this number is strongly dependant of the number of Cells I chose. Do you have any idea of what I am doing wrong? In advance thank you Olivier

Re: Replica and energy density deposition by michel maire <michel maire>, Jul 09, 04:17 Re: Replica and energy density deposition (Olivier Dadoun) On Tue, 07 Jul 2009 10:02:26 GMT, Olivier Dadoun wrote: > Hello, > > I am studying the energy density deposition (unit in MeV/mm3) inside a Target of Tungsten. > To do so I have segmented my target in N_Cell_z*N_Cell_x*N_Cell_y which are my elementary volumes (using Replica Volume). > I retrieved the cell hits using > G4int NrX = aStep->GetPreStepPoint()->GetTouchable()->GetReplicaNumber(1); > G4int NrY = aStep->GetPreStepPoint()->GetTouchable()->GetReplicaNumber(2); > G4int NrZ = aStep->GetPreStepPoint()->GetTouchable()->GetReplicaNumber(0); > and the cumulated deposited energy is > depESum[NrZ][NrX][NrY] += aStep->GetTotalEnergyDeposit(); > > Finally I fill a 3D histo using ROOT. > > I am interested in the Peak Energy Density Deposition, i.e the maximum > value of depESum divided by the volume of the elementary cell volume. > > My problem is that this number is strongly dependant of the number of > Cells I chose. Do you have any idea of what I am doing wrong? > > In advance thank you Olivier > Shower shape must not depend too much of cell's granularity ... - what amount of variation are you speaking about ? - what is typical size of the cells ? - what is the incident energy ? We have test-examples to study shower shape (al least in 1 dimension). Try to reproduce your results with TestEm2 or TestEm11 (in examples/extended/electromagnetic) Michel

Re: Replica and energy density deposition by Olivier Dadoun <Olivier Dadoun>, Jul 09, 05:36 Re: Re: Replica and energy density deposition (michel maire) Hello Michel, I have a Tungsten target of 2.5cm*2.5cm*1.2cm. I use for exemple 100 MeV of e- beam energy to impinge on this target (normal incidence with a gaussian spatial distribution in X and Y with a sigma of 1.6mm). If took 0.025*0.025*0.012cm3 as elementary volume: I found a maximum energy of 8.41 MeV, so 8.41/(0.025*0.025*0.012)=1.1e6MeV/cm3, If I took 0.05*0.05*0.024cm3 as elementary volume: I found a maximum energy of 27.4 MeV, so 27.4/( 0.05*0.05*0.024)=4.56e5MeV/cm3. There is 60% of difference between maximum energy density. Thank you Olivier PS:I will have a look on TestEm2 and TestEm11.

Re: Replica and energy density deposition by michel maire <michel maire>, Jul 10, 08:17 Re: Re: Replica and energy density deposition (Olivier Dadoun) Both examples compute 1D longitudinal shower profile (called also depth dose distribution). I ran TestEm11 with following macro : # # limit the step size from histo 1 # /control/verbose 2 /run/verbose 2 # /testem/det/setMat G4_W /testem/det/setSizeX 12 mm /testem/det/setSizeYZ 25 mm # /testem/phys/addPhysics standard # em physics # /run/initialize # /gun/particle e- /gun/energy 100 MeV # /testem/histo/setFileType root ###/testem/histo/setFileType hbook /testem/histo/setFileName dadoun.120um /testem/histo/setHisto 1 100 0. 12. mm #edep profile # /testem/event/printModulo 10000 # /run/beamOn 100000 Bin size was 60um, 120um, 240um Plot is in attachement. Position and value of the maximum are unchanged. Cordialement, Michel Attachment: http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/07/10/08.13-56403-dadoun.pdf

Re: Replica and energy density deposition by Olivier Dadoun <Olivier Dadoun>, Jul 12, 15:14 Re: Re: Replica and energy density deposition (michel maire) Hello Michel, thank you for your answer. I found also the same results concerning the energy per unit of length (along the beam axis propagation). My problem is more on the transverse plane: What will you obtain for the energy density if you now apply some segmentations on the tranverse plane? D'avance merci Olivier

Re: Replica and energy density deposition by michel maire <michel maire>, Jul 15, 04:00 Re: Re: Replica and energy density deposition (Olivier Dadoun) On Sun, 12 Jul 2009 22:14:57 GMT, Olivier Dadoun wrote: > Hello Michel, > > thank you for your answer. > > I found also the same results concerning the energy per unit of length > (along the beam axis propagation). > > My problem is more on the transverse plane: > > What will you obtain for the energy density if you now apply some > segmentations on the tranverse plane? TestEm11 has no lateral segmentation, but TestEm2 has (cylindrical geometry). Dadoun.txt is a cylinder of tungsten, radius 3 X0 (X0=3.5 mm) radial segmentation dr= 52 um, 105 um, 210 um. Plot of dE/dr distribution in attachement. Apart for the first bin (central cylinder), the distributions are identical. In fist bin, energy density is dependent of the bin size (here radius), as you observed. Variation ~30% from 52 um to 210 um. For small cell size, this effect is inherent to multiple scattering and cannot be avoid. However the effect must be relativised. More signifiant is the total energy deposited within a cylinder of given radius. See second plot. Total energy deposited within radius ~0.1 X0 is almost identical for the 3 segmentations. Attachment: http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/07/15/03.50-33067-dadoun.txt http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2009/07/15/03.51-60046-dadoun.pdf

Re: Replica and energy density deposition by Olivier Dadoun <Olivier Dadoun>, Jul 21, 01:13 Re: Re: Replica and energy density deposition (michel maire) Merci Michel. I decided to change a little bit my simulation following your example TestEm2. My volume is now sliced virtually (don't use anymore Replica), and in my Sensible Detector the energy deposition is spread along a step: G4ThreeVector pos = prePoint + G4UniformRand()*(postPoint - prePoint); G4double edep = aStep->GetTotalEnergyDeposit(); and I fill my 3D root histo rootOutput.GetHisto3D()->Fill(xpos,ypos,zpos,edep); (binning is control by my input file) I have still my problem on my energy density deposition:( but now my simulation is really faster :). I read you talk http://geant4.in2p3.fr/2007/prog/MichelMaire/testem_series.pdf. Page 17-18 you said the step size < histogram binning, and you give two plots one with constraint on step and the other one without. What you mean by "constraint on step" ? Merci pour ta patience Olivier

Output to matlab by Shawn Sbannist <Shawn Sbannist>, Jun 16, 10:00 Does anyone have a suggestion for how to force geant to output a matlab compatible file such as a .csv, I would need it to be done for a very high number of simulations. I am using a calorimeter geometry and I want to have outputs that are some kind of an image that portrays the track and energy of each individual particle in each simulation.

Re: Output to matlab by Guy Barrand <Guy Barrand>, Jun 17, 01:20 Re: Output to matlab (Shawn Sbannist) Hello Shawn To store what ? an ntuple ? If so, then you have to look / ask to the AIDA implementers to provide a "csv driver" for asii ntuples. Right now in the OpenScientist AIDA implementation I have a "space separated" ascii output for ntuple. For example for a tuple with 3 columns : 1 2 3 4 5 6 .... which can be read with various analysis interactive programs (also with some fight) from mathematica. In fact, you can probably see, to produce suche file and then have some little shell script tool to convert it to a "comma" separated file... And if a "comma separated" is usefull then I can see to arrange my things... Cheers Guy

The Methods ListObjectNames and ListObjectTypes of AIDA? by <bgastro@pmo.ac.cn>, Jun 07, 19:49 Hi everyone, I installed AIDAJNI-3.2.2 and JAIDA-3.2.3 to analysis the outputs, it worked well for the Geant4 extended example A01. But it fell into the memory error once I use the method listObjectNames and listObjectTypes of ITree. Could anybody help me out? ps: my gcc version is 4.1.2 and geant is 4.8.1.p02. Many thanks in advance.

using AIDA-3.2.1 by <tintin73>, Jun 01, 00:51 Dear Geant4 gurus, I've only just started to use GEANT4 (on Windows XP). I am trying to run the Brachtherapy application which works fine ...until I try to do some analysis using the aida tool. I've downloaded to tool to [ c:/AIDA ] and unzipped the tarfile [ aida-3.2.1.tar.gz ]. I am unsure how to link this to GEANT4 so that when I switch on [G4ANALYSIS_USE=1 ], I stop getting the error message [ /bin/sh:aida-config: command not found.. ] I think I need a config script i.e an aida-setup script? Not sure where to get this. Also, how do I actually use the AIDA tool to analysis an output file for example the .aida file that should be generated by the A01 application? Do I dump the file in my C:/AIDA directly and run from there? Could someone point me in the right direction please? Thanks a lot.

Serious discepency between Geant4.7.0.p01 and Geant4.9.1.p03 by Pradip Datta <Pradip Datta>, May 29, 03:37 Dear All, I have generated a output file contains the detector no and the corresponding energy. I have opened the file in RunAction and write data in EventAction. Things are perfectly working in Geant4.7.0.p01. I have tested it with 500000 events where I shoot a gamma ray of fixed energy randomly within a defined cone. Interestingly when I am trying to run the program in Geant4.9.1.p03, it is working perfectly but gives a segmentation fault when the output file size is reached exactly 8k. I have a compulsion to use Geant4.7.0.p01 and hence I write every part of the code first in 4.7.0.p01 then try to run it in Geant4.9.1.p03. Till date it runs perfectly in every stage but fails recently at this stage. Does anybody has any idea about the problem? Regards, Pradip

Writing output by Pradip Datta <Pradip Datta>, 14 May, 2009 Hi All, I have made a segmented Ge detector. For this purpose I have modified the novice prog N02. If I set the tracking verbosity to "1", I am getting output about the energy deposition, copy no of the segment and other outputs listed in ExN02SteppingVerbose.cc (I have add only one line to extract the information about the segment no). Now I would like to write the energy and segment no in a output file. To be specific, I would like to generate a zero suppressed unformatted binary data file for further analysis. I have little understanding (I admit) about the architecture and the data flow between the hits and events in Geant4. Such limited knowledge really makes it difficult for me decide where should I include the fwrite statement to write the data. Probably, I can always do it in SteppingVerbose.cc file within the tracking verbosity=1 loop. In that case, I have to comment all the G4out statement in side the tracking verbosity=1 loop to avoid writing in stdout instead I should include fwrite(.....fStep->GetPreStepPoint()->GetTouchableHandle()->GetCopyNumber()....) and fwrite(....fStep->GetTotalEnergyDeposit()......) But I don't thinks this is the correct way to do this job. I really need an expert advise about my problem. Thus, I appreciate any sorts of input. With regards, Pradip

Re: Writing output by Paul Nicholas Colin Gloster <Paul Nicholas Colin Gloster>, 14 May, 2009 Re: Writing output (Pradip Datta) On Thu, 14 May 2009, Pradip Datta wrote: |--------------------------------------------------------------------------------| |"[..] For this purpose I have modified | |the novice prog N02. If I set the tracking verbosity to "1", I am | |getting output about the energy deposition, copy no of the segment and | |other outputs listed in ExN02SteppingVerbose.cc (I have add only one | |line to extract the information about the segment no). Now I would like | |to write the energy and segment no in a output file. To be specific, I | |would like to generate a zero suppressed unformatted binary data file | |for further analysis. | | | |I have little understanding (I admit) about the architecture and the | |data flow between the hits and events in Geant4. Such limited knowledge | |really makes it difficult for me decide where should I include the | |fwrite statement to write the data. | | | |Probably, I can always do it in SteppingVerbose.cc file within the | |tracking verbosity=1 loop. In that case, I have to comment all the G4out | |statement in side the tracking verbosity=1 loop to avoid writing in | |stdout instead I should include | | | |fwrite(.....fStep->GetPreStepPoint()->GetTouchableHandle()->GetCopyNumber()....)| | | |and | | | |fwrite(....fStep->GetTotalEnergyDeposit()......) | | | |But I don't thinks this is the correct way to do this job. I really need | |an expert advise about my problem. Thus, I appreciate any sorts of | |input." | |--------------------------------------------------------------------------------| An alternative method which you can exploit is void ExN02SteppingAction::UserSteppingAction(const G4Step*) in ExN02SteppingAction.cc and another is G4bool ExN02TrackerSD::ProcessHits(G4Step* aStep,G4TouchableHistory*) in ExN02TrackerSD.cc . With kind regards, Paul Colin Gloster

Number of Photons vs Energy by Antonio Magalhaes <Antonio Magalhaes>, 29 Apr, 2009 I have a primitive setup to generate x-rays (target, filters, etc). Now, I want to detect those photons and create an analysis system (hbook, ascii, JAS...whatever) that show-me the number of photons in function of its energy, however i'm beginer with geant and don't know how to do it... there's some example or "light" for my problem? I apreciate your help! so thanks!

OpenScientist Problems? by <bgastro@pmo.ac.cn>, 13 Apr, 2009 Hi everyone, I downloaded the OpenScientist(osc_vis-v16r0-Linux-ia32-gcc_34.zip) and unpacked it. Then I installed it following the suggestions of the README file in the directory OpenScientist which is unpacked from the osc_vis-v16r0-Linux-ia32-gcc_34.zip: 1)./install 2)source ~/OpenScientist/v16r0/aida-setup.sh Then I switched to the examples/extended/Analysis/a01 and did the following procedures: 1)source setup-analysis.sh 2)make clean 3)make I got some warning as following: >... >include/A01AnalysisManager.hh:56: Warning: declaration 'class AIDA::IAnalysisFactory' did not declare anything >include/A01AnalysisManager.hh:57: Warning: declaration 'class AIDA::ITree'did not declare anything >... >Linking A01app... >...Done! Then I switched to my work directory, tried to execute A01app: ./A01app I got the error messages like following: >Lib::DLL::DLL : can't load OnXTestDLD library. >Lib::DLL::DLL : error : libOnXTestDLD.so: cannot open shared object file: No >such file or directory >Lib::DLL::DLL : can't load BatchLabXML library. >Lib::DLL::DLL : error : libBatchLabXML.so: cannot open shared object file: No >such file or directory >BatchLab::TreeFactory::loadTree : unable to add a DLL >segment fault could anyone help me through this? ps: my OS is Fedora 10 and gcc version is 4.3.2

Can not book root file or hbook file, by <viet.nga.thi.la@cern.ch>, 01 Apr, 2009 Hello, I test TestEm1 and TestEm3 in examples/extended/electromagnetic, Geant4 can't book the root or hbook file in my computer. But in other computer, Geant4 can do it. Do the geant4 in my computer have a problem ? Do you have experimences? Help-me! Viet Nga

OpenScientist installation problems by <Santos>, 27 Feb, 2009 I am trying to install OpenScientist on a Ubuntu 7.10 machine with Geant4 and CLHEP already installed. I wanted the osc-vis package; to be on the safe side I decided to install from source. I followed procedure described on the web site http://openscientist.lal.in2p3.fr/, in the "build from source" part. 1) Unzipped OpenScientist 2) Switched to OpenScientist/16.8/osc_vis/16.8/obuild directory 3) Ran . ./setup.sh (I use BASH) 4) Ran ./sh/build I was able to get through most of the installation without much of a problem (Synaptic/apt-get in Ubuntu are great). The real problem came when the system tried to build the geant4 part. It tries to find CLHEP in /usr/local/CLHEP/2.0.3.2 and certainly fails (well, at some point I put a link to my CLHEP, version 2.0.4.0 there, it was satisfied but got stuck with some other problem on geant4). As it is recommended on the site, I went to OpenScientist/16.8/foreign/v1r7p0 and edited CLHEP.obuild: <variable name="CLHEP_home" platform="UNIX">PUT REAL PATH HERE</variable> and also, just in case <native_version>PUT MY VERSION HERE</native_version> Still, I get the same: "WARNING : CLHEP not found under /usr/local/CLHEP/2.0.3.2" message. This is even more surprising because I changed the message, so, even if the system somehow looks into /usr/local/CLHEP/2.0.3.2, the message should look different. Then I also tried to find where else in the package there is a phrase "WARNING : CLHEP not found under ..." and could not. Now I am really stuck and puzzled. Could somebody, please, tell me what is going on and how to fix this. Thank you, Slava

Re: OpenScientist installation problems - SOLVED by <Santos>, 03 Mar, 2009 Re: OpenScientist installation problems Here I'm summarizing my off-line exchange with Guy Barrand. To make sure the system is aware of the changes one makes in "package".obuild file, one needs to execute obuild on that file. For example, the initial problem concerned CLHEP.obuild (and later Geant4.obuild) file, which enters G4Lab group. Then, after editing corresponding *.obuild files (CLHEP.obuild and Geant4.obuild) do: cd ../../../G4Lab/<version>/obuild ../../../obuild/<version>/bin_obuild/obuild sh/build -v -group Geant4 where -v is a useful "verbose" option that will allow you to see that your changes were indeed implemented. After the group is built, you can do the general build: cd ../../../osc_vis/<version>/obuild (to return back to osc_vis) ../../../obuild/<version>/bin_obuild/obuild sh/build_release The last command will create a zip file containing ready to install (osc_vis) kit. It's in osc_vis/<version>/bin_obuild Move it to the place of your liking, unzip and then cd <your path>/osc_vis/<version> ./install Your distribution should be ready to go. To start it, you need to source the setup file (need to either put it in your profile or rc file or source it for every shell where you want to use the kit): . <your path>/osc_vis/<version>/setup.sh (for bash shells) After which you can run any of the programs: osc-plot, osc-g4-vis, etc

Geant4 example A01 Linking Problem by Lisandro Martinez <Lisandro Martinez>, 08 Dec, 2008

I am new to Geant4 and I am trying to construct the A01 example, I have compiled the example and used WIRED to see the particle trajectories and so forth. When I try to start with the An alysis section I get an error in the linking of A01app
I am working on a: MacOS 10.5.5 i686-apple-darwin9 gcc version 4.0.1 JAIDA 3.2.1 AIDAJNI 3.2.1
My Environment is:
export G4WORKDIR=/Applications/geant4work
export DYLD_LIBRARY_PATH=/Applications/CLHEP/osx105_ia32_gcc401/lib
export G4INSTALL=/Applications/geant4.9.1.p03
source /Applications/geant4.9.1.p03/env.sh
export JAVA_HOME=/Library/Java/Home
export JDK_HOME=/Library/Java/Home
export JAIDA_HOME=/Applications/AIDA/JAIDA-3.2.1
source $JAIDA_HOME/bin/aida-setup.sh
export AIDAJNI_HOME=/Applications/AIDA/AIDAJNI-3.2.1
export AIDAJNI_LIBS=/Applications/AIDA/AIDAJNI-3.2.1/lib/Darwin-g++
source $AIDAJNI_HOME/bin/Darwin-g++/aidajni-setup.sh
export G4ANALYSIS_USE=1
When I type make clean and make
the program starts Making dependency and compiling, but when it gets to the linking I get this

Linking A01app ... ld warning: in /Applications/AIDA/AIDAJNI-3.2.1/lib/Darwin-g++/libAIDAJNI.a, file is not of required architecture ld warning: in /Applications/AIDA/AIDAJNI-3.2.1/lib/Darwin-g++/libFHJNI.a, file is not of required architecture Undefined symbols: "_AIDA_createAnalysisFactory", referenced from: A01AnalysisManager::A01AnalysisManager()in libA01app.a(A01AnalysisManager.o) ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [/Applications/geant4work/bin/Darwin-g++/A01app] Error 1

Any Ideas of how to solve this! Thank you very much in advance.
Lisandro

Problems compling analysis A01 by Jamie Wright <Jamie Wright>, 21 Nov, 2008 Dear all, I have downloaded JAIDA(3.2.1) and AIDAJNI(3.2.3) and setup the environment thus: export JAIDA_HOME=<my path>/JAIDA-3.2.1 source $JAIDA_HOME/bin/aida-setup.sh export AIDAJNI_HOME=<my path>/AIDAJNI-3.2.3 source $AIDAJNI_HOME/bin/Linux-g++/aidajni-setup.sh I have also installed java sdk and set the environment variable for that. When I come to compile analysis A01 however I get errors such as: /bin/sh: aida-config: not found And a lot of other errors stemming from this. Anyone else ever had this problem? thanks Jamie

Analysis using only ROOT by Jamie Wright <Jamie Wright>, 13 Nov, 2008 Dear All A simple question I think however I'm new to geant4, ROOT and Linux in general. I want to create histograms to analyse with ROOT. After searching the forums I discovered thread #187 which describes my situation exactly. I modified exN02 with the new SD files however when I come to compile I get errors such as "TFile.h:no such file or directory". Do I need to add ROOT to my path or configure the enviroment in some way? I have added to the makefile CPPFLAGS += -I$(ROOTSYS)/include EXTRALIBS = $(shell root-config --glibs) Any suggestions would be appreciated Thanks Jamie

Re: Analysis using only ROOT by Christina Zacharatou <Christina Zacharatou>, 16 Nov, 2008 Re: Analysis using only ROOT (Jamie Wright) For setting the environment variables, please see http://root.cern.ch/root/EnvVars.html Christina

Re: Analysis using only ROOT by Jamie Wright <Jamie Wright>, 20 Nov, 2008 Re: Re: Analysis using only ROOT (Christina Zacharatou) Christina Thanks for the reply. ROOT is working on my machine yet I still can't get the example to run. I may have to install JAIDA or another package and try analysis that way

Re: Analysis using only ROOT by Christina Zacharatou <Christina Zacharatou>, 20 Nov, 2008 Re: Re: Analysis using only ROOT (Jamie Wright) Hi You can find some instructions on how to do that in the following example: /geant4.9.2.b01/examples/extended/electromagnetic/TestEm7 in the file InstallAida.txt. Christina

Re: Analysis using only ROOT by Christina Zacharatou <Christina Zacharatou>, 20 Nov, 2008 Re: Re: Analysis using only ROOT (Christina Zacharatou) Btw, if you don't want to use Java, you could also install iAIDA instead: http://iaida.dynalias.net/Intro.html

Re: Analysis using only ROOT by Jamie Wright <Jamie Wright>, 21 Nov, 2008 Re: Re: Analysis using only ROOT (Christina Zacharatou) The problem with the root example was in the ROOTSYS variable. I am running on a university machine with root preinstalled and I guess not properly installed. A way to get root output is to change the makefile line: CPPFLAGS += -I$(ROOTSYS)/include with: CPPFLAGS += -I$(shell root-config --incdir) This may be a help to anyone using university machines with root preinstalled. Thanks to Ivana Hrivnacova for this solution Jamie

Re: Analysis using only ROOT by Jason Brudvik <Jason Brudvik>, 23 Dec, 2008 Re: Re: Analysis using only ROOT (Jamie Wright) Just wanted to add something to this discussion. I too had some problems getting root to cooperate properly with geant, it turned out that my root-config, which was located /bin/root-config, was an old version, leftover from a previous installation of root. My solution to this was similar to what others have already shown: CPPFLAGS += -I$(ROOTSYS)/include/ EXTRALIBS = $(shell $(ROOTSYS)/bin/root-config --glibs) which assumes of course that the environment variable ROOTSYS is set properly, but if for some reason it's not, then you can just state the paths explicitly. For example, if you have your newest version of root installed in /usr/local cern/root/ : #CPPFLAGS += -I/usr/local/cern/root/include/ #EXTRALIBS = $(shell /usr/local/cern/root/bin/root-config --glibs) This way, you get around any problems with ROOTSYS be improperly set or an old root-config being used.

Hadrontherapy ROOT output by Jonathan Mbewe <Jonathan Mbewe>, 12 Nov, 2008 Hallo all I have used iAIDA in the Geant4 Hadrontherapy example to produce a .ROOT file with the histograms and ntuples. My problem is that I would able to draw histograms to show cross-plane dose profiles at different depths along the beam axis (x-axis) in the 3D matrix. I am quite new to ROOT. Can anyone help? Thanks. Jonathan

OpenScientist version for Ubuntu 8.04.1 by Angela Intermite <Angela Intermite>, 23 Oct, 2008 Dear all, I have Linux-i386-gcc 423 and Ubuntu 8.04.1. I searched in the kits of OpenScientist for installing it but there is no kit suitable for my gcc.Could I know if it exists a version of OpenScientist suitable for me? Or should I change my version of Linux? Thank you very much angela

Re: OpenScientist version for Ubuntu 8.04.1 by Guy Barrand <Guy Barrand>, 10 Dec, 2008 Re: OpenScientist version for Ubuntu 8.04.1 (Angela Intermite) Hello Angela I have released an OSC 16.8 and in principle I have done modifications to build on an ubuntu. (Done on a virtual machine by using VirtualBox on my Mac). osc_batch kit : ------------- The construction of the osc_batch kit went fine since being standalone over C++. Only some warnings to correct coming from the 4.2.4 (up so fare I compiled only up to 4.0.1 on my Mac). I remember that the osc_batch kit are targeted to create histos and tuples, fill them and save them in files at various formats. And this by using the AIDA API. No GUI and graphics here. I have strongly revisited my web pages, and the "First AIDA program" and "AIDA and Geant4" sections should permit to start quickly for that. (Things are more "tutorial" and "how to" oriented now). osc_vis kit : ----------- More things had to be done to run on ubuntu. Mainly because, contrary to the Scientific Linuxes, the X11 libs are not under /usr/X11R6/lib but are "returned back" under /usr/lib. I had to change things in my build system to detect that automatically. In fact it seems that X11 "being back" under /usr/lib is also what is done on Fedoras. Then the modifs in the build done for ubuntu should works also for a build from source of the osc_vis 16.8. For the binaries then I have put the two : osc_batch-16.8-Linux-i386-gcc_424.zip osc_vis-16.8-Linux-i386-gcc_424.zip that I have built on my virtual machine. 4.2.4 is what I get with apt-get and is a little bit ahead to your 4.2.3. You can try anyway. If not working try to build from source (or attempt to upgrade a bit your compiler :-) ) For infos, to rebuild the osc_vis from source with all the drivers, I had to install o g++ (that was not here by default from the ubuntu from VirtualBox). o OpenMotif suite : (it is the default GUI of an osc_vis). libmotif3, libxt-dev, libxmu-dev, libxext-dev, libxp-dev, libxpm-dev, libxi-dev. o OpenGL : libglu1, libosmesa6-dev o python-dev (2.5.2). o libqt4-dev (4.3.4) o libgtk1.2-dev, gtkglarea5-dev. o libsdl1.2-dev, libcurl4-gnutls-dev. (Only the OpenMotif and OpenGL suite is in fact needed by default to do some visualization for Geant4 by using the osc-g4-vis program and related tools (see below)). By using the Synaptic GUI to apt-get, you can select all the uppers and ask to install at once. It went nice for me. (Synaptic is found for me under the desktop menu : "System/Administration/Synaptic package manager") osc-g4-vis : ---------- Concerning Geant4, the 16.8 comes with a new little (but important) program, the : osc-g4-vis It permits to instrument automatically some of the G4 examples (today the novices, A01, AnaEx01, head of exgps and exrdm now) to have a high level GUI and graphics (done by using Inventor / coin3d) targeted for G4. In principle with that you should be able to have in a swift : - a default wire frame visualization. - manipulate it with the nice Inventor 3D viewer. - a tree widget to see the geometry. - choose a PV (PhysicalVolume) in the tree and visualize it. - strat a run with the mouse or with G4 commands. - see the trajectories - pick all that and have some feedback infos. - loop on events (and see them flashing around). - produce PS, VRML or inventor files. but also in case of doing some AIDA histos and tuples (for exa with A01, TestEm1) : - plot the histograms within the same GUI. - see the histos to be filled on line. - manipulate the tuple with the TupleExplorer. - build some views that mix volumes with plots. The program modifies the G4 local GNUmakefile and the main to do what is needed. Whence applied, it is sufficient to simply rebuild the exa with make and run. (Nothing else to learn). The program should work also at once on other user programs that are clones of some of the mentionned examples. See the page "osc-g4-vis" for more, then at : http://OpenScientist.lal.in2p3.fr (there is a lot of pictures too) Let me know in case of problems. Cheers Guy

TestEm examples by Morthekai <Morthekai>, 20 Aug, 2008 Hi, After successful compilations of TestEm2, 7, 11 examples, I got error messages like, Lib::DLL::DLL : can't load BatchLabZebra library. Lib::DLL::DLL : error : /{HOME}/osc_batch/v16r0/bin/libBatchLabZebra.so: undefined symbol : _ZNK8BatchLab9BaseTuple8rowIndexEv BatchLab::TreeFactory::loadTree : unable to add a DLL BatchLab::TreeFactory::create_tree : can't create "testem2.hbook" during execution. This kind of error appeared for *.aida file as well. But if I follow Ivana's suggestion by adding CPPFLAGS += -I$(ROOTSYS)/include EXTRALIBS = $(shell root-config --glibs) in the makefile, the execution suddenly stopped by showing that kind of error. I have ROOT installed and OpenScientist batch, as suggested in the forum, is also have in my PC (OS: fc7). Could you please help me in this regard? Thanks and regards, Morthekai

Re: TestEm examples by Guy Barrand <Guy Barrand>, 12 Dec, 2008 Re: TestEm examples (Morthekai) Hello I have tested the AIDA of TestEm2,7, 11 on various machines and it is ok for me. It is ok too with the osc 16.8 I have released this week. Can you try again for example with the osc_batch 16.8 on your machine ? Don't know what went wrong with the 16.5 on your machine so that you have not the CERNLIB/Zebra driver. It is a classical problem : - or you attempt to run a binary kit that does not match your platform. What is the kind of distrib you use ? (Still FC7 ?) What is the exact version of g++? What did you try to do exactly ? - or you have build a osc_batch / osc_vis kit from source and have missed something around the building of the "Zebra driver / group". I have revisited my web pages for the 16.8. In particular the way to build from source received more explanations (in particular on how to build code related to "foreign" / "external" software). If really nothing works for you, give me you exact platform, I can attempt to have a virtual machine of it... What is sure, is that you have first to attempt to use OSC / AIDA without having ROOT around. This may add an extra layer of problems. Then attempt to build and run by having not ROOT in your PATH, not in LD_LIBRARY_PATH and not activated in the GNUmakefile. In case of problems it is always good to separate things and activate the minimum of what is related to the problem. (In fact you can also build and run by having G4VIS_NONE set to 1 to desactivate the G4/visualization and then run only by using the G4 kernel). Let me know here or offline... Cheers Guy

exRDM exaple and histogramming. by Vladimir Kulikovskiy <Vladimir Kulikovskiy>, 07 Aug, 2008

Dear experts,
I am trying now to get output file in .root or .aida with histograms and data, which is described in README for this example.
And I really stuck with choosing analysing tool - iAIDA doesn't compile, PI is not easy thing to compile too (I was not succeded). Last versions of AIDAJNI doesn't compile with Maven 2.08 and 2.09... and so on.
Some positive experience was with: JAIDA3.2.4+AIDAJNI3.2.3, also with Open Scientist (batch), that was compiled by my own or already compiled. But in all situations I get next errors:
--- fileType is unknown variable. I changed it to histType and compiling was fine, but when linking I've got errors like this:
$ make clean
Cleaning up ...
$ . ~/geantfiles/osc_batch-v16r5/osc_batch/v16r5/aida-setup.sh
$ export G4ANALYSIS_AIDA_CONFIG_CFLAGS=`aida-config --cflags`
$ export G4ANALYSIS_AIDA_CONFIG_LIBS=`aida-config --libs`
$ export G4ANALYSIS_USE=1
$ export G4ANALYSIS_USE_AIDA=1
$ make
****************************
Compiling exRDM.cc ...
Linking exRDM ...
/home/qvoffka/geant4/tmp/Linux-g++/exRDM/exe/exRDM.: In function
`G4VisExecutive::RegisterModelFactories()':
exRDM.cc:(.text+0x99): undefined reference to `G4TrajectoryGenericDrawerFactory::G4TrajectoryGenericDrawerFactory()'
exRDM.cc:(.text+0xa5): undefined reference to `G4VisManager::RegisterModelFactory(G4VModelFactory<G4VTrajectoryModel>*)'
exRDM.cc:(.text+0xbb): undefined reference to `G4TrajectoryDrawByChargeFactory::G4TrajectoryDrawByChargeFactory()'
What analysing tool is the most usable now? How to install and compile everything to get .aida or .root file in this example (after I could enjoy working with them with ROOT or JAS3 which are very usable)?
Help from anybody, who have positive experience in running this example with analysing tools is very appreciated.

exRDM / AIDA part reviewed / osc_batch 16.8 by Guy Barrand <Guy Barrand>, 12 Dec, 2008 Re: exRDM exaple and histogramming. (Vladimir Kulikovskiy) Hello Vladimir Just to say that I had a review with the author of exrdm concerning the AIDA part and we have corrected various things that were not correct concerning the usage of AIDA. In particular now the program holds in case of doing multiple runs within the same session. Then if you have access to the G4 repository it could be fine to have a try by using the head of exRDM. If you think you have problems with the visualization you can attempt to build and run by setting the env variable G4VIS_NONE to 1 that disconnect it at all. When convinced that the example is ok for you by using only the G4 kernel + AIDA then you may attempt to run by restoring the vis later. Else concerning OpenScientist (that were not in the things you tried :-( Snif ) then you can attempt to use the "osc_batch kit" which is something very light (without any interactive things) that should permit you to write files at the .hbook, . root, .aida formats. (See http://OpenScientist.lal.in2p3.fr ) I have binary kits for it. If you platform is not too exotic you may try a binary kit. I have released this week an OSC 16.8. I have strongly revisited the web pages that are more "tutorial" and "how to" oriented now and have dedicated sections concerning AIDA and AIDA and Geant4. In particular the review of AIDA in exRDM (along the one done on exGPS and others) had been done with this release. Then I am interested in feebacks of others with exRDM (then taken at head) here. Cheers Guy

Re: exRDM exaple and histogramming. by John Allison <John Allison>, 07 Aug, 2008 Re: exRDM exaple and histogramming. (Vladimir Kulikovskiy) Those undefined references are nothing to do with analysis. They suggest that somehow the relevant library is not being found or there exists an old library. I think that before you go further it would be good to rebuild Geant4 with a consistent environment. (Possibly, the problem was caused by changing environment; after a change of environment, code should be recompiled.)

Re: exRDM exaple and histogramming. by Vladimir Kulikovskiy <Vladimir Kulikovskiy>, 08 Aug, 2008 Re: Re: exRDM exaple and histogramming. (John Allison) Thanks for the answer. I tried set all the environment as in begin of my first post. After I made ./Configure -build && ./Configure -install in geant folder. Do you think, it's enough for recompiling geant? After I tried to make exRDM example. The same result. What analysis software do you use? And what version of geant? Are you able to compile exRDM without changing fileType to histoType in exrdmHisto.cc and can you get .aida file after running it? Thanks in advance for answer.

Re: exRDM exaple and histogramming. by Patrick Sizun <Patrick Sizun>, 08 Aug, 2008 Re: Re: exRDM exaple and histogramming. (Vladimir Kulikovskiy) Hello, On my installation, this example only builds with AIDA after removing these lines from the GNUmakefile : ifdef G4ANALYSIS_USE_AIDA CPPFLAGS += -DG4ANALYSIS_USE_AIDA CPPFLAGS += `aida-config --include` LDLIBS += `aida-config --lib` endif and of course configuring the AIDA osc_batch environment : setenv G4ANALYSIS_USE 1 setenv G4ANALYSIS_AIDA_CONFIG_CFLAGS `aida-config --cflags` setenv G4ANALYSIS_AIDA_CONFIG_LIBS `aida-config --libs` Regards, Patrick

Re: exRDM exaple and histogramming. by John Allison <John Allison>, 08 Aug, 2008 Re: Re: exRDM exaple and histogramming. (Vladimir Kulikovskiy) After installation you have to set your environment. See Installation Guide, Section 2.2.

Re: exRDM exaple and histogramming. by Vladimir Kulikovskiy <Vladimir Kulikovskiy>, 08 Aug, 2008 Re: Re: exRDM exaple and histogramming. (John Allison) Thanks for the answer. I tried set all the environment as in begin of my first post. After I made ./Configure -build && ./Configure -install in geant folder. Do you think, it's enough for recompiling geant? After I tried to make exRDM example. The same result. What analysis software do you use? And what version of geant? Are you able to compile exRDM without changing fileType to histoType in exrdmHisto.cc and can you get .aida file after running it? Thanks in advance for answer.

Warning appears when OpenScientist installed by Xinxin Tang <Xinxin Tang>, 04 Aug, 2008 Hi, After i installed OpenScientsit(version is :osc_vis-v16r5-Linux-i386-gcc_323.zip),warning appers when i compile An01,i don't know how to fix it. any suggestion will be appreciated! the following is warning message. /usr/bin/ld: warning: libstdc++.so.5, needed by /home/txx/program/OpenScientist/v16r5/lib/libOnXLabAIDA.so, may conflict with libstdc++.so.6

Re: Warning appears when OpenScientist installed by Guy Barrand <Guy Barrand>, 05 Aug, 2008 Re: Warning appears when OpenScientist installed (Xinxin Tang) Hello You are in a typical situation where the platform used to build the binary kit does not match the one of your platform. The warning about libstdc++ comes from a mismatch of the version of g++ between the one I have used to build the binary kit and the one of your machine. For this kit, I have used a g++-3.2.3 on an Intel 32 bits. Then what is your compiler version and kind of machine ? If I can put the hand on a similar machine I can build for you the osc_vis binary kit. Else the best is that you attempt to build the osc_vis kit from source. (Then see instructions on the web pages). Best Regards Guy Barrand

Un able to create "big" aida analysis files. by Or Chen <Or Chen>, 26 Jul, 2008 Hey, My analysis job consist of 4 graphs and n-tuples. when i'm trying to analyze 2.5 million events everything works fine, when I'm moving on to 3 million it creates and empty .aida file. Is it a known problem? If so, what's the solution? because my final destination is to analyze 10^8 events. Thnks' Or.

Re: Un able to create by Guy Barrand <Guy Barrand>, 05 Aug, 2008 Re: Un able to create "big" aida analysis files. (Or Chen) I have answered offline, but could be fine to post something here too. I don't know if JAIDA implementation has limitation, but what I can say is that the OpenScientist 16.5 (and then the osc_batch-16.5), which is available since end of July (2008), permits now to write big files (more than 2 Giga) if saving at the ROOT format.

how to add energy resolution code in geant4 by ylzhang <ylzhang>, 25 Apr, 2008 I have a question. Mono energy alpha particles entrance silicon detector. I can gain a spectrum. and fit the spectrum, gained a FWHM. but i didnot put the energy resolution in the material. If I put the energy resolution that could be gained from experiment into code. runaction->eventInfo.siliconLayersEnergyDepositWithError[ptr] = runaction->eventInfo.siliconLayersEnergyDeposit[ptr] + RandGaussT::shoot( engine, 0.0, sqrt( siliconSigma[ptr]*siliconSigma[ptr] + siliconNoise*siliconNoise ) the FWHM is bigger than experiment. and the resolution of the simulation spectrum is different from the experiment. so i donnot the code is right, i donnot know how to set the energy resolution that could gained a spectrum that is similar to the spectrum of experiment.

Re: how to add energy resolution code in geant4 by John Allison <John Allison>, 28 Apr, 2008 Re: how to add energy resolution code in geant4 (ylzhang) Why do you want to add resolution? At each step, Geant4 gives a deposited energy that is drawn from the appropriate distribution - the Landau distribution - for that particle in that material. So its distribution - with some addition, perhaps, for electronic readout noise - should match your observed distribution. You should think of the addition of electronic readout noise as a separate step, nothing to do with Geant4. It is often referred to as "digitisation". Geant4 just does the physics.

Re: how to add energy resolution code in geant4 by ylzhang <ylzhang>, 01 May, 2008 Re: Re: how to add energy resolution code in geant4 (John Allison) ok, thanks.

The problem with histogram and PI Keywords: histogram, PI by <yfdeng@student.dlut.edu.cn>, 08 Apr, 2008 Hello, I have a problem about extend example named fanoCavity2 which used histogram to analyse data. Before I compile it, I have installed the AIDA implementation "AIDA-JNI" and "JAIDA" as 7th instruction mentioned in its readme file. However, I can't get the histogram still. What's the reason? How to cope with it? And I try to install the PI implementation, but I don't know how to set the environment(on the web site, there said only need to set the environment). Could you give me a detail instruction about it? My verion of PI is PI_1_3_12 and it is released in d:/PI. My system is windows+cygwin. Thank you very much. Please forgive my poor English.

Re: The problem with histogram and PI Keywords: histogram, PI by michel maire <michel maire>, 08 Apr, 2008 Re: The problem with histogram and PI User wrote: >> Hello, >> I have a problem about extend example named fanoCavity2 which used histogram to analyse data. Before I compile it, >> I have installed the AIDA implementation "AIDA-JNI" and "JAIDA" as 7th instruction mentioned in its readme file. >> However, I can't get the histogram still. What's the reason? How to cope with it? Note that, by default, histograms are disabled. To activate them, uncomment the flag G4ANALYSIS_USE in GNUmakefile. Did you that before to compile ? >> And I try to install the PI implementation, but I don't know how to set the environment(on the web site, there said >> only need to set the environment). Could you give me a detail instruction about it? My verion of PI is PI_1_3_12 and it >> is released in d:/PI. My system is windows+cygwin. >> Thank you very much. Please forgive my poor English. >> If you have ROOT or cernlib/paw already installed, an alternative to PI or JAIDA is to use the AIDA part of OpenScientist Here is the last part of the #249 of this forum : I confirm Jean-Etienne Sauvestre experience. Under Scientific Linux, download binaries from : http://openscientist.lal.in2p3.fr/download. Download and gunzip : http://openscientist.lal.in2p3.fr/download/16.0/osc_batch-v16r0-Linux-i386-gcc_323.zip Installation: prompt%> cd osc_batch/v16r0 prompt%> ./install prompt%> source aida-setup.csh OpenScientist batch is a small package ( ~ 6MB), easy to install. It is a reasonable alternative to PI for those which have ROOT and/or PAW already installed. Jean Jacquemier

Re: The problem with histogram and PI Keywords: histogram, PI by <yfdeng@student.dlut.edu.cn>, 09 Apr, 2008 Re: Re: The problem with histogram and PI (michel maire) Thank you very much for your reply. Maybe I haven't write a clear statement. I have set the G4ANALYSIS_USE=1 when I comipled the example. However,I can't get the histogram. The same mistake comes when I compile the TestEm* example. So I don't know what to cope with it. Could you help me? I also read some messages of this forum, but I still can't resolve my problem. Thank you! Best regards! Y.F.Deng

Re: The problem with histogram and PI Keywords: histogram, PI by michel maire <michel maire>, 09 Apr, 2008 Re: Re: The problem with histogram and PI independently of Geant4, have you ROOT or PAW (cernlib) already installed ?

Re: The problem with histogram and PI Keywords: histogram, PI by <yfdeng@student.dlut.edu.cn>, 09 Apr, 2008 Re: Re: The problem with histogram and PI (michel maire) Hello Michel Maire, Thank you very much! I really haven't installed Root or PAW. Now I know your means. I must firstly install the Root or PAW and then installed the OpenScientist instead of PI. Am I right? Best regards! Thank you again! Y.F.Deng

Re: The problem with histogram and PI Keywords: histogram, PI by michel maire <michel maire>, 09 Apr, 2008 Re: Re: The problem with histogram and PI User wrote: >> Hello Michel Maire, >> Thank you very much! I really haven't installed Root or PAW. Now I know your means. >> I must firstly install the Root or PAW and then installed the OpenScientist instead of PI. Am I right? >> Best regards! Thank you again! >> Y.F.Deng >> Yes. Only the batch version of OpenScientist: it is enough.

Re: The problem with histogram and PI Keywords: histogram, PI
by <yfdeng@student.dlut.edu.cn>, 09 Apr, 2008
Re: Re: The problem with histogram and PI (michel maire)

Hello, Thank you for your qiuck reply. I have installed the Root and OpenScientist. The environment has been set. Everything seems to be well installed. However, when I come to compile the FanoCavity2, there gives a error. The whole error message is given below. I must mention that the AIDA hasn't installed in my system, but AIDAJNI and JAIDA implementations have been carefully installed.The environments have also been set. The list of error: -----error about histoclean--------------- $ make histoclean Making dependency for file fanoCavity2.cc ... Making dependency for file src/TrackingAction.cc ... Making dependency for file src/SteppingVerbose.cc ... Making dependency for file src/SteppingAction.cc ... Making dependency for file src/StepMaxMessenger.cc ... Making dependency for file src/StepMax.cc ... Making dependency for file src/RunAction.cc ... Making dependency for file src/PrimaryGeneratorAction.cc ... Making dependency for file src/PhysicsListMessenger.cc ... Making dependency for file src/PhysicsList.cc ... Making dependency for file src/MyMollerBhabhaModel.cc ... Making dependency for file src/HistoMessenger.cc ... Making dependency for file src/HistoManager.cc ... Making dependency for file src/EventActionMessenger.cc ... Making dependency for file src/EventAction.cc ... Making dependency for file src/DetectorMessenger.cc ... Making dependency for file src/DetectorConstruction.cc ... make: *** No rule to make target `histoclean'. Stop. -----------error about compile----------

$ make

Compiling DetectorConstruction.cc ...

DetectorConstruction.cc

Compiling DetectorMessenger.cc ...

DetectorMessenger.cc

Compiling EventAction.cc ...

EventAction.cc

Compiling EventActionMessenger.cc ...

EventActionMessenger.cc

Compiling HistoManager.cc ...

HistoManager.cc

src/HistoManager.cc(37) : fatal error C1083: can not open include files:“AIDA/AIDA.h”: No such file or directory
make: *** [c:/geant4/tmp/WIN32-VC/fanoCavity2/HistoManager.o] Error 2

So, what's the reasons? Is it due to the absent of AIDA? Thank you again

How to mention resolution of detector? by Anil <Anil>, 04 Feb, 2008 Hello, Iam interested to simulate the response of NaI for gamma rays. Is it possible to obtain a realistic gaussian-like energy peak curve by giving energy dependant FWHM (due to noise, statistics, etc.)? In what part of the codes can we mention for this purpose? Thanks in advance!

Re: How to mention resolution of detector? by Maria Grazia Pia <Maria Grazia Pia>, 05 Feb, 2008 Re: How to mention resolution of detector? (Anil) The Geant4 xray_fluo advanced example illustrates how to model a detector response, like energy dependent resolution, efficiency etc. Best regards, Maria Grazia Pia

Untitled Keywords: resolution by Anil <Anil>, 04 Feb, 2008 Hello, Iam interested to simulate the response of NaI for gamma rays. Is it possible to obtain a realistic gaussian-like energy peak curve by giving energy dependant FWHM (due to noise, statistics, etc.)?In what part of the codes can we mention for this purpose? Thanks in advance!

please very emergency:how can i create a spectrum??? Keywords: create a spectrum by elif <elif>, 22 Jan, 2008 ciao dear friends; i did a detector setup. I have two Ge detectors and i can do interaction with them.. But i have a probleam.. After interaction how can i create a spectrum? please help me:(( ciao, chylec..

Re: please very emergency:how can i create a spectrum??? Keywords: create a spectrum by John Allison <John Allison>, 26 Jan, 2008 Re: please very emergency:how can i create a spectrum??? (elif) Use the General Particle Source. See examples/extended/eventgenerator/exgps. The manual is accessible from item 10(a) on the Geant4 User Support page.

rAIDA in Hadrontherapy example by Jonathan Mbewe <Jonathan Mbewe>, 14 Jan, 2008

I have installed the latest version of rAIDA. Upon ´making´ the hadrontherapy example I get the following error;

Linking Hadrontherapy ... /usr/local/g4work//tmp/Linux-g++/Hadrontherapy/libHadrontherapy.so: undefined reference to `AIDA_createAnalysisFactory'
collect2: ld returned 1 exit status make: *** [/usr/local/g4work//bin/Linux-g++/Hadrontherapy] Error 1

Can anyone help?

Jonathan

Medical Linac analysis problem Keywords: MedlinacDiane.xml analysis MedLinac by Carlo Nicolini <nicolini.carlo@gmail.com>, 12 Jan, 2008 Hi, I'm using MedLinac advanced example. I've set G4ANALYSIS_USE and I use JAIDA 3.2.1 and AIDAJNI 3.2.1. gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) When I compile and use A01 example, everything is ok and I produce A01.aida file Using MedLinac example, I obtain only one file MedLinacDiane.xml of 555 byte. (I noticed that a file of similar dimension is produced by A01 app with /run/beamOn 1) Analyzing it with Jas3, that open it, I see that's a file containing only the titles of the histograms but no data. I suppose that something goes wrong with the filling of the histograms, isn'it? I appreciate any ideas. Thank you Carlo Nicolini

Medical Linac analysis problem Keywords: MedlinacDiane.xml analysis MedLinac by Carlo Nicolini <nicolini.carlo@gmail.com>, 12 Jan, 2008 Hi, I'm using MedLinac advanced example. I've set G4ANALYSIS_USE and I use JAIDA 3.2.1 and AIDAJNI 3.2.1. gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) When I compile and use A01 example, everything is ok and I produce A01.aida file Using MedLinac example, I obtain only one file MedLinacDiane.xml of 555 byte. (I noticed that a file of similar dimension is produced by A01 app with /run/beamOn 1) Analyzing it with Jas3, that open it, I see that's a file containing only the titles of the histograms but no data. I suppose that something goes wrong with the filling of the histograms, isn'it? I appreciate any ideas. Thank you Carlo Nicolini

The simplest analysis with Root in Geant4 by Aivaras <aivaras.zukauskas@gmail.com>, 04 Dec, 2007 Hello, I apologize for a silly question since you guys have a lot of job to do, but can you help me with the simplest analysis in Geant4 using Root? For example, to create a histogram or something similar. Does anyone know some web addresses where it could be explained with examples? I tried to look into /extended examples, but I can't compile most of them, because AIDA or PI is used - I don't have them. Thankyou.

Re: The simplest analysis with Root in Geant4 by Jacquemier Jean <Jacquemier Jean>, 04 Dec, 2007 Re: The simplest analysis with Root in Geant4 (Aivaras) aivaras, you could install OpenScientist batch which provides AIDA implemention. Installation instructions can be find here: http://geant4-hn.slac.stanford.edu:5090/HyperNews/public/get/analysis/249/3/3/1/1/1/1.html Regards, Jean Jacquemier

Re: The simplest analysis with Root in Geant4 by Aivaras <aivaras.zukauskas@gmail.com>, 06 Dec, 2007 Re: Re: The simplest analysis with Root in Geant4 (Jacquemier Jean) Thankyou for a good advise, but I prefer Root more.

Re: The simplest analysis with Root in Geant4 by Ivana Hrivnacova <Ivana Hrivnacova>, 06 Dec, 2007 Re: Re: The simplest analysis with Root in Geant4 (Aivaras) You can use directly Root classes from your Geant4 application. See the thread #187 for more details. Best regards, Ivana

Segmentation fault in aidajni in 64-bit enviroment Keywords: aidajni segmentation faults 64-bit by Per <f99-pfo@f.kth.se>, 01 Nov, 2007 Dear All! Modifing exampel A01 I started getting segmentation faults. Fast forward, looking back at the vanilla A01 example and running it thought gdb I'm getting segmentation fault but the program keeps running! Can anyone try this as well? 64-bit enviroment, compile and run A01 with G4ANALYSIS_USE set try vis.mac Does it run? Does Geant4 quit correctly? Now run it thought gdm. Any errors? /Per Fogelstrom

file results by Ibrahim <Ibrahim>, 22 Oct, 2007 Hi, During the run of my program i can obtain the energy deposit in the detector and the position of this energy. I’d like to output these results in a file. How can i do it? With best regards

JAS3 by Ibrahim <Ibrahim>, 18 Oct, 2007 Hi, I run my program , a file called .aida is created, when i open it with jas3, i can see the spectrum of gammas. I want to integrate the surface under the gaussian curve. how can i do it with jas3 ? I'd like also to know the number of gammas that have interacted with photoelecticeffect , compton scattering und so on how can i do it . thank you very much regards

RE: JAS3 by <tony_johnson@slac.stanford.edu>, 18 Oct, 2007 Re: JAS3 (Ibrahim) > I run my program , a file called .aida is created, when i > open it with jas3, i can see the spectrum of gammas. I want > to integrate the surface under the gaussian curve. how can i > do it with jas3 ? HI Adam, I think from your question and your earlier questions on the JAS3 mailing list that you might need to understand the basics of how histograms work. Wikipedia might be a good starting point: http://en.wikipedia.org/wiki/Histogram Basically when you histogram a quantity x, you see a plot which shows the number of entries in each bin in x. In the statistics box you will see the mean value of x, the RMS which is a measure of the spread around x, and the entries, which is the total count of entries you made in the histogram. The entries is basically equaivalent to the total area under the curve. You can also do a guassian fit to your histogram from that get the gaussian parameters corresponding to your curve. If you have more questions about JAS3 specific features I would suggest posting them on the JAS3 discussing forum at: http://forum.freehep.org/index.php?t=thread&frm_id=3 If you also attach your .aida file there and explain in a little more detail what you want to achieve we can probably help more. Tony

Re: JAS3 by michel maire <michel maire>, 18 Oct, 2007 Re: JAS3 (Ibrahim) User Adam wrote: > >> I'd like also to know the number of gammas that have interacted with photoelecticeffect , compton scattering und so on >> how can i do it . In examples/extended/electromagnetic/TestEm1/include you will find a class called ProcessesCount, used by RunAction and SteppingAction. (see the log file TestEm1.out) Michel

AIDA_creatAnalysisFactory Keywords: AIDA_createAnalysisFactory air_shower
by Oscar Larsson <Oscar Larsson>, 04 Oct, 2007

Hi

I doing my diploma work at the moment so I'm very new to Geant4 but I've manage to get it working, almost.
When I compile the advanced example air shower I get the following error message:

Compiling Ultra.cc ...
Using granular libraries ...
Linking Ultra ...
/home/oscar/geant4/tmp/Linux-g++/Ultra/libUltra.so: undefined reference to `AIDA_createAnalysisFactory'
collect2: ld returned 1 exit status
make: *** [/home/oscar/geant4/bin/Linux-g++/Ultra] Error 1

What is wrong??? What, and how do I have to do, to fix this problem??
This is the same problem mentioned in topic No. 21 but the reply “I'd solved it already.” needless to say, didn't help me much...

So, please please please help me.

/Oscar
oscarlar(at)kth(dot)se

ROOT and Geant4 Keywords: ROOT Geant4 by Luke <lucas.snyder@gmail.com>, 07 Sep, 2007 Hello, I have Geant4 and ROOT working on my windows machine but I cannot seem to get them to work together. I get the following error when I try to make a simple histogram. ...... fatal error C1083: Cannot open include file: 'TH1.h': No such file or directory ...... I assume it is a problem with my makefile and I have tried several of the variations I have seen on this forum and others but nothing seems to work. Can anyone help? My current makefile looks like this ...... ifdef ROOTSYS ifdef G4UI_USE_ROOT CPPFLAGS += $(shell $(ROOTSYS)/bin/root-config --cflags) ROOTLIBS = $(shell $(ROOTSYS)/bin/root-config --glibs) -lMinuit -lHtml ROOTLIBS := $(filter-out -lNew,$(ROOTLIBS)) ROOTLIBS := $(filter-out -lThread,$(ROOTLIBS)) ROOTLIBS := $(filter-out -lpthread,$(ROOTLIBS)) LDFLAGS += $(shell root-config --libs) LDLIBS += $(ROOTLIBS) endif endif ...... Thanks Luke

problem about read ITuple from a aida file Keywords: AIDA, file manipulate, ITuple by long <long>, 15 Aug, 2007 Dear experts, I wrote some codes to read out ITuple data from a aida file by referencing thread #163. It could find the designated tuple object from the file, but it could not read out the data in the tuple. I don't know why. The following is part of the codes. Some notes beside the instruction command. AIDA::ITuple *oldTuple; . . . AIDA::IManagedObject* managedObject2= oldTree->find("./Tuple2"); if(!managedObject2) // being skipped { G4cout<<"this pointer is NULL:"<<G4endl; exit(4); } else // will be executed { G4cout<<"managedObject2 pointer is pointed to:"<<managedObject2->name()<<G4endl; oldTuple = (AIDA::ITuple*)managedObject2->cast("AIDA::ITuple"); } G4cout << "there are "<<oldTuple->rows() <<" in the radionuclides table"<<G4endl; // the return value of rows() is zero, but acutally,there are 3596 rows in that Tuple oldTuple->start(); while ( oldTuple->next() ) // being skipped. Seems that oldTuple is a empty tuple { double time = oldTuple->getDouble(1); // created time of radionuclides double weight = oldTuple->getDouble(2); //weight vecHisto[1]->fill(time,weight); // fill the IHistogram1D with a value and the corresponding weight }

some more information on AIDA Keywords: AIDA, file manipulate, ITuple by long <long>, 16 Aug, 2007 Re: problem about read ITuple from a aida file (long) Sorry I forgot to mention my AIDA implementation. The whole enviroment is AIDAJNI-3.2.4, jaida-3.3.0-5, gcc version 4.1.1 20070105 (Red Hat 4.1.1-51). Jdk1.5.0.11. Hope these will be helpful to find out the answer.

2D Histogram of particle's endpoint position Keywords: 2D histogram, xy plane, particle endpoint
by Matthew Middione <middionematt@csufresno.edu>, 17 Jul, 2007

I am looking to plot a 2D Histogram of the endpoint position of a particle. I am using TestEm1 (GEant/examples/extended/TestEm1) to do my simulation and a portion of the output is seen below: ********************************************************************************************************* * G4Track Information: Particle = F18[0.0], Track ID = 1, Parent ID = 0 ********************************************************************************************************* Step# X Y Z 0 0 fm 0 fm 0 fm 1 0 fm 0 fm 0 fm ********************************************************************************************************* * G4Track Information: Particle = e+, Track ID = 4, Parent ID = 1 ********************************************************************************************************* Step# X Y Z 0 0 fm 0 fm 0 fm 1 -5.89 um 2.58 um 29.8 um 2 -10.2 um 3.71 um 37.9 um 3 -43.3 um 40.4 um 108 um 4 -106 um 75.4 um 218 um 5 -110 um 84.5 um 226 um 6 -120 um 102 um 244 um 7 -120 um 102 um 244 um 8 -125 um 109 um 253 um 9 -142 um 124 um 289 um 10 -162 um 148 um 323 um 11 -174 um 161 um 345 um 12 -192 um 196 um 375 um 13 -204 um 212 um 405 um 14 -276 um 331 um 518 um 15 -261 um 397 um 645 um 16 -246 um 397 um 630 um 17 -220 um 413 um 611 um 18 -176 um 411 um 615 um 19 -171 um 362 um 634 um 20 -172 um 358 um 630 um 21 -155 um 338 um 605 um 22 -156 um 338 um 601 um 23 -151 um 341 um 590 um 24 -147 um 342 um 584 um 25 -147 um 342 um 583 um 26 -144 um 329 um 574 um 27 -144 um 327 um 573 um 28 -144 um 327 um 573 um What I want to do is plot the x and y position of the e+ positrons just before they annihilate with an electron. This endpoint position is the very last line seen above in the output. Is there a way that I cn histrogram this data and run the event 50,000 times and get a plot in Geant? Thanks, Matthew Middione

creating histograms of variable bin widths using JAIDA by Victor_Makarov <Victor_Makarov>, 04 Jul, 2007 Hi! I'd like to create histograms of variable bin widths using JAIDA. I've looked into JAida documentation and found the proper command for that: "createHistogram1D(String path, String title, double[] binEdges) " where binEdges is an array. Using Java it is supposed to set binEdges like that: double[] binEdges = {0,0.1,0.21,0.35,0.48,0.52,0.65,0.75,0.83,0.94,1.0}. But C++ wouldn't understand that. But if I use double binEdges[] (recognizable by C++), AIDA wouldn't understand it. So, what is that command supposed to be? Thanks.

Re: creating histograms of variable bin widths using JAIDA by Mark Donszelmann <Mark Donszelmann>, 04 Jul, 2007
Re: creating histograms of variable bin widths using JAIDA (Victor_Makarov)

Hi Victor, java uses arrays (as we can determine their lengths). In c++ you need to use std::vector<double> (because we cannot determine the length of a c++ array). vector<double> binEdges; binEdges.push_back(0); binEdges.push_back(0.1); ... binEdges.push_back(1.0); but maybe there is a better way to init this vector. Greetings Mark Donszelmann On Jul 4, 2007, at 6:40 AM, Victor wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/295"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Hi! I'd like to create histograms of variable bin widths using JAIDA. > I've looked into JAida documentation and found the proper command for > that: "createHistogram1D(String path, String title, double[] > binEdges) " > where binEdges is an array. Using Java it is supposed to set binEdges > like that: double[] binEdges = > {0,0.1,0.21,0.35,0.48,0.52,0.65,0.75,0.83,0.94,1.0}. But C++ wouldn't > understand that. But if I use double binEdges[] (recognizable by C++), > AIDA wouldn't understand it. So, what is that command supposed to be? > Thanks.

Re: creating histograms of variable bin widths using JAIDA by Victor_Makarov <Victor_Makarov>, 05 Jul, 2007 Re: Re: creating histograms of variable bin widths using JAIDA (Mark Donszelmann) (Robocop-like voice...) Thank You for your cooperation! That did work!

memory error when creating many Histogram1D's by Victor_Makarov <Victor_Makarov>, 04 Jul, 2007

Hi! I wanted to create 4 Histogram1D's for my analysis (before that I worked with 2 - it was ok) I have tested my example on 2 platforms: Windows+Cygwin+Jaida (AIDAJNI-3.2.3 and JAIDA-3.2.4) and Sc.Linux 4.4 + Jaida. Both times my program run crashes complaining about memory (Linux message - *** glibc detected *** malloc(): memory corruption (fast): 0x0913a518 ***)! I don't know. Maybe I have my RunAction not written in a proper way but I inherited it from one of the examples and just wanted to use some more histograms. Here are the parts of it responsible for histograms:

RunAction::RunAction() :af(0), tree(0) { histo[0] = 0; histo[1] = 0; histo[2] = 0; histo[3] = 0;

#ifdef G4ANALYSIS_USE // Creating the analysis factory af = AIDA_createAnalysisFactory();

if (af) { // Creating the tree factory AIDA::ITreeFactory* tf = af->createTreeFactory();

// Creating a tree mapped to an hbook file. G4bool readOnly = false; G4bool createNew = true; G4String options = "--noErrors uncompress"; tree = tf->create("testem4.XML" ,"XML" ,readOnly,createNew, options); delete tf;

if (tree) { // Creating a histogram factory AIDA::IHistogramFactory* hf = af->createHistogramFactory(*tree);

// Creating the histogram histo[0]=hf->createHistogram1D ("1","Neutrons reaching detector with energies 0-1 keV",140,0.1,14.1); histo[1]=hf->createHistogram1D ("2","Neutrons reaching detector with energies 1-100 keV",140,0.1,14.1); histo[2]=hf->createHistogram1D ("3","Neutrons reaching detector with energies 100-1000 keV",140,0.1,14.1); histo[3]=hf->createHistogram1D ("4","Neutrons reaching detector with energies more than 1 MeV",140,0.1,14.1);

delete hf; G4cout << "\n----> Histogram tree is opened" << G4endl; } } #endif } When I reduce to 3 histograms the executable manages to run without memory errors. Don't pay attention to parameters of Histogram1D's.

Thanks.

Re: memory error when creating many Histogram1D's by Victor_Makarov <Victor_Makarov>, 06 Jul, 2007 Re: memory error when creating many Histogram1D's (Victor_Makarov) Shame on me! Just forgot to set histo[4] in .hh file!

Re: memory error when creating many Histogram1D's by Kazuyoshi Furutaka <Kazuyoshi Furutaka>, 04 Jul, 2007 Re: memory error when creating many Histogram1D's (Victor_Makarov) Hi Victor, From: "Victor" <douglas@slac.stanford.edu> Subject: memory error when creating many Histogram1D's Date: Wed, 4 Jul 2007 02:11:44 -0700 > tree = tf->create("testem4.XML" ,"XML" ,readOnly,createNew, options); You created a tree in a XML file: as I understand correctly, when saving into a XML file, the tree data won't be flushed and accumulated in memory of your machine until a run ends, and eventually exhaust it. Just stop runs periodically. Kazuyoshi -- Kazuyoshi Furutaka furutaka@jb3.so-net.ne.jp

Re: memory error when creating many Histogram1D's by Andreas Pfeiffer <Andreas Pfeiffer>, 04 Jul, 2007 Re: Re: memory error when creating many Histogram1D's (Kazuyoshi Furutaka) Hi Kazuyoshi, >> tree = tf->create("testem4.XML" ,"XML" ,readOnly,createNew, >> options); > > You created a tree in a XML file: as I understand correctly, > when saving into a XML file, the tree data won't be flushed > and accumulated in memory of your machine until a run ends, > and eventually exhaust it. this is true if you deal with Tuples (and unbinned Histograms if there is no limit set for them for auto-conversion), but for binned Histograms (as is the case here) this is not an issue they have a fixed memory footprint. cheers, andreas

Re: memory error when creating many Histogram1D's by Kazuyoshi Furutaka <Kazuyoshi Furutaka>, 04 Jul, 2007 Re: Re: memory error when creating many Histogram1D's (Andreas Pfeiffer) Hi Andreas From: "Andreas Pfeiffer " <andreas.pfeiffer@cern.ch> Subject: Re: memory error when creating many Histogram1D's Date: Wed, 4 Jul 2007 06:46:41 -0700 > >> tree = tf->create("testem4.XML" ,"XML" ,readOnly,createNew, > >> options); > > > > You created a tree in a XML file: as I understand correctly, > > when saving into a XML file, the tree data won't be flushed > > and accumulated in memory of your machine until a run ends, > > and eventually exhaust it. > > this is true if you deal with Tuples (and unbinned Histograms > if there is no limit set for them for auto-conversion), but > for binned Histograms (as is the case here) this is not an > issue they have a fixed memory footprint. Ah, I misunderstood... Kazuyoshi -- Kazuyoshi Furutaka furutaka@jb3.so-net.ne.jp

Re: memory error when creating many Histogram1D's by Andreas Pfeiffer <Andreas Pfeiffer>, 04 Jul, 2007
Re: memory error when creating many Histogram1D's (Victor_Makarov)

Hi Victor, > [...] > Jaida. Both times my program run crashes complaining about memory > (Linux > message - *** glibc detected *** malloc(): memory corruption (fast): > 0x0913a518 ***)! I don't know. Maybe I have my RunAction not > written in this message is normally an indication that somewhere in your program you write beyond allowed/allocated memory causing other parts of the program to be overwritten. It is only by coincidence that the fourth histogram triggers this as booking it changes the memory-layout. You could try to run the program inside a memory checking program (on linux try valgrind for example) to see where the problem is. cheers, andreas

Re: memory error when creating many Histogram1D's by Victor_Makarov <Victor_Makarov>, 04 Jul, 2007 Re: Re: memory error when creating many Histogram1D's (Andreas Pfeiffer) First, thanks for response. Second, as I'm not strong in Linux, could You provide more information on valgrind usage? How do I run it together with my G4 executable? Thanks in advance.

Re: memory error when creating many Histogram1D's by Andreas Pfeiffer <Andreas Pfeiffer>, 04 Jul, 2007 Re: Re: memory error when creating many Histogram1D's (Victor_Makarov) > First, thanks for response. Second, as I'm not strong in Linux, could > You provide more information on valgrind usage? How do I run it > together > with my G4 executable? Thanks in advance. Good documentation is available from the valgrind web page, for example the "QuickStart Guide" at: http://valgrind.org/docs/manual/QuickStart.html There are also other links to documentation under: http://valgrind.org/docs/ There must also be some tool with a similar functionality to valgrind available for windows, but I don't know, maybe others can help here.

Where can I get Java for Jaida? by Victor_Makarov <Victor_Makarov>, 28 Jun, 2007 Hi guys. Untill now there was a very good tutorial dealing with JAIDA installation posted here: http://geant4.slac.stanford.edu/g4cd/August2005/Documentation/WorkshopExercises/Exercise5.html But seems to be they update... On that page there was a link for Java download (J.d.k. 1.5 if not mistaken). I can't find it by myself. Can You help? I use Scientific Linux 4.4. Thanks. And where was http://www-sldnt.slac.stanford.edu/G4CD moved to?

RE: Where can I get Java for Jaida? by <tony_johnson@slac.stanford.edu>, 28 Jun, 2007 Re: Where can I get Java for Jaida? (Victor_Makarov) HI, > Hi guys. Untill now there was a very good tutorial dealing > with JAIDA installation posted here: > http://geant4.slac.stanford.edu/g4cd/August2005/Documentation/ > WorkshopExercises/Exercise5.html I am not sure what has happened to those pages, we will try to get them restored. > But seems to be they update... On that page there was a link > for Java download (J.d.k. 1.5 if not mistaken). I can't find > it by myself. Can You help? You should be able to download Java for all platforms from http://java.sun.com/javase/downloads/index.jsp JAIDA should work with either Java 1.5 or 1.6. Unfortunately Sun keeps changing the name of these products to confuse people, these are currently refered to as JDK 6u1 (Java 1.6) Previous Releases -> J2SE5.0 -> JDK 5.0 Update 12 (Java 1.5) > I use Scientific Linux 4.4. > Thanks. And where was http://www-sldnt.slac.stanford.edu/G4CD > moved to? I don't think that link has worked for a long time? It was replaced with the http://geant4.slac.stanford.edu/g4cd you refer to above. Tony

RE: Where can I get Java for Jaida? by Joseph Perl <Joseph Perl>, 28 Jun, 2007 Re: RE: Where can I get Java for Jaida? I removed the g4cd symlink myself two days ago because users looking for basic Geant4 installation information were finding this extremely outdated information and so getting totally messed up in their installations. I apologize for messing up these AIDA links in the process, but I am quite surprised that any information from so long ago could still be appropriate. It would be better to just move the AIDA parts to an appropriate AIDA area. The rest of the material on that CD is entirely out of date and so quite dangerous. Can you clarify which pages are actually still useful? Joseph

RE: Where can I get Java for Jaida? by <tony_johnson@slac.stanford.edu>, 28 Jun, 2007 Re: RE: Where can I get Java for Jaida? (Joseph Perl) Hi Joe, > I removed the g4cd symlink myself two days ago because users > looking for basic Geant4 installation information were > finding this extremely outdated information and so getting > totally messed up in their installations. > > I apologize for messing up these AIDA links in the process, > but I am quite surprised that any information from so long > ago could still be appropriate. > > It would be better to just move the AIDA parts to an > appropriate AIDA area. The rest of the material on that CD is > entirely out of date and so quite dangerous. > > Can you clarify which pages are actually still useful? All of the information about setting up and using AIDA/JAIDA is still appropriate and still works. We have pointed many people to these pages, when they ask us questions by e-mail, and when discussions occur on the forum, and there are many links from google etc to these pages. I am perfectly happy for you or someone else to add a comment at the top that they have not been updated recently, and to point to your new installation instructions, but I don't think your new instructions address this issue. Meanwhile I think the pages still contain useful information. We are currently holding an AIDA workshop at SLAC, and one of the issues we have been working on is improved instructions for setting up AIDA for Geant4. We plan to combine the OpenScientist instructions with the AIDA/JAIDA content from the g4cd area and produce new unified instructions, but it will likely be a couple of months before these are ready. At that point we could perhaps remove the old g4cd area (but it would be good to do it in such a way that people are directed to the new instructions, rather than just sent to a dead link). Tony

RE: Where can I get Java for Jaida? by Joseph Perl <Joseph Perl>, 28 Jun, 2007 Re: RE: Where can I get Java for Jaida? I've restored the link for now. But I disagree with your statement that dead links are worse than outdated information. The information contained in this outdated CD is extremely misleading to new users. They are better off not finding this information and so following other links that lead to more accurate information. Once a user has done an incorrect installation of Geant4, especially when it involves hand-setting of environment variables rather than using the offical configure script, they can have a very hard time getting back to a useful starting point. The instructions also include such things as outdated Cygwin information, which again can cause users many days of wasted effort. Please identify the useful subset of this information so that the harmful information can be removed as soon as possible.

RE: Where can I get Java for Jaida? by Victor_Makarov <Victor_Makarov>, 28 Jun, 2007 Re: RE: Where can I get Java for Jaida? (Joseph Perl) Thank You guys for quick response. I'm sorry to see some misunderstanding... I was talking about http://geant4.slac.stanford.edu/g4cd/August2005/Documentation/WorkshopExercises/Exercise5.html. Thanks for restoring it. It's really useful and still actual...

Modifying histograms in TestEm3 example Keywords: histograms by Konstantinos Michael <Konstantinos Michael >, 15 Jun, 2007 Hi all, I have successfully create the XML file type and read it with jas3(Thanks to Marks' advise!). I have also created the 4 types of histograms that testem3 can provide. How can i create more types of histograms such as clouds for example? Can i have examples A01 code as guide? What class should i modify in testem3? Thanks

Re: Modifying histograms in TestEm3 example by Vladimir IVANTCHENKO <vnivanch@mail.cern.ch>, 15 Jun, 2007
Re: Modifying histograms in TestEm3 example (Konstantinos Michael )

On Fri, 15 Jun 2007, Konstantinos Michael wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/289"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Hi all, > > I have successfully create the XML file type and read it with > jas3(Thanks to Marks' advise!). I have also created the 4 types of > histograms that testem3 can provide. > > How can i create more types of histograms such as clouds for example? > > Can i have examples A01 code as guide? > > What class should i modify in testem3? > > Thanks > Hello, We usually advise do not modify our examples but copy and start doing you rown application basing on the example. If you do so, you are absolutly free any part of application. IN particular add whatever hisogram you need. regards, VI

Re: Modifying histograms in TestEm3 example by Konstantinos Michael <Konstantinos Michael >, 18 Jun, 2007 Re: Re: Modifying histograms in TestEm3 example (Vladimir IVANTCHENKO ) Thanks VI, I did copy the example and tried to do my own application but still i don't know how to create a histogram and use it into the Geant4 code. Is there any example i can take as a guide? thanks

Re: Modifying histograms in TestEm3 example by Vladimir IVANTCHENKO <vnivanch@mail.cern.ch>, 19 Jun, 2007
Re: Re: Modifying histograms in TestEm3 example (Konstantinos Michael )

On Mon, 18 Jun 2007, Konstantinos Michael wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/289/1/1"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Thanks VI, > > I did copy the example and tried to do my own application but still i > don't know how to create a histogram and use it into the Geant4 code. Is > there any example i can take as a guide? > > thanks > Hello, Use TestEm3 as an example. Other examples can be used as well. A short explanation what histogram are inside TestEm3 is in README file for the example. VI

Re: Modifying histograms in TestEm3 example by michel maire <michel maire>, 18 Jun, 2007 Re: Re: Modifying histograms in TestEm3 example (Konstantinos Michael ) User Konstantinos Michael wrote: >> Thanks VI, >> >> I did copy the example and tried to do my own application but still i >> don't know how to create a histogram and use it into the Geant4 code. Is >> there any example i can take as a guide? >> >> thanks TestEm4 is the simplest case of the testEm serie

Re: Modifying histograms in TestEm3 example by Maria Grazia Pia <Maria Grazia Pia>, 18 Jun, 2007 Re: Re: Modifying histograms in TestEm3 example (Konstantinos Michael ) You can have a look at various Geant4 advanced examples (e.g. geant4/examples/advanced/brachytherapy, /hadrontherapy, /medical_linac, /xray_fluorescence) and their associated README file; some documentation on how to deal with histograms and tuples in Geant4 applications is also available from http://www.ge.infn.it/geant4/examples. Best wishes, Maria Grazia Pia

Making some histograms for ROOT by Adam <ax_blais@laurentian.ca>, 12 Jun, 2007

I am using the example found here: ftp://root.cern.ch/root/IcaG4.tar/gz

I transferred the Analysis.cc class to one of my own programs. I have set my environment variable, namely G4ANALYSIS_USE_ROOT = 1 but when running I get no histograms at all. It's as if the ROOT code isn't even there. I tried using a cout to figure out the problem, and it appears that my code is ignoring whatever is inside the "if defined".

You can see that my G4cout comes right after the if defined.

void ExN02Analysis::OnceAWhileDoIt(const G4bool DoItNow) {

time_t Now = time(0); // get the current time (measured in seconds) if ( (!DoItNow) && (LastDoItTime > (Now - 10)) ) return; // every 10 seconds LastDoItTime = Now;

#if defined (G4ANALYSIS_USE_ROOT) G4cout << "ROOT IS BEING DONE" << G4endl;

TVirtualPad *CurrentPad = gPad;

const char OnceAWhileCanvas[] = "ExN02AnalysisCanvas";

TCanvas *c = (TCanvas *)gROOT->GetListOfCanvases()->FindObject(OnceAWhileCanvas);

if ( DoItNow && (!c) && ((G4RunManager::GetRunManager())->GetVerboseLevel() > 1) ) { // first, try to make sure we do not run in batch mode if (!gApplication) new TApplication("Application", ((int *)0), ((char **)0)); // then, create the TCanvas c = new TCanvas(OnceAWhileCanvas, OnceAWhileCanvas); if (c) { c->Divide(2,2); c->cd(1); if (hStepLength) hStepLength->Draw(); c->cd(2); if (hStepTotELoss) hStepTotELoss->Draw(); c->cd(3); if (hOPWaveLength) hOPWaveLength->Draw(); c->cd(4); if (hTotELossNorm) hTotELossNorm->Draw(); c->cd(0); } }

if (c) { //c->cd(0); c->Draw(); c->Update(); } G4cout << "ROOT IS BEING DONE" << G4endl; TFile f("g4hist.root", "new"); hStepLength->Write(); if (CurrentPad) CurrentPad->cd();

if (gSystem) gSystem->ProcessEvents();

#endif /* defined (G4ANALYSIS_USE_ROOT) */ }

I get no output like this. However, if I put the cout before that line, like this:

void ExN02Analysis::OnceAWhileDoIt(const G4bool DoItNow) { G4cout << "ROOT IS BEING DONE" << G4endl;

time_t Now = time(0); // get the current time (measured in seconds) if ( (!DoItNow) && (LastDoItTime > (Now - 10)) ) return; // every 10 seconds LastDoItTime = Now;

#if defined (G4ANALYSIS_USE_ROOT)

TVirtualPad *CurrentPad = gPad;

I get the output with this. I don't understand why this isn't working. Like I said, my environment variable is set so I don't know what's wrong.

extended_hadronic_Hadr01 / OpenScientist-16.0 / empty histos in .hbook file by Guy Barrand <Guy Barrand>, 24 May, 2007 Hello We have seen, with Jean-Etienne Sauvestre of CEA, that on : extended/hadronic/Hadr01 of the 8.2, the "hbook" persistency done by using the Zebra driver of OpenScientist-16.0 produces a p_pb_20gev.book files with empty histos ! This comes from the fact that in this example (see Histo::save() code), someone do : tree->commit(); tree->close(); for(G4int i=0; i<nHisto; i++) { if(histo[i]) histo[i]->reset(); } That is to say, a reset() is done over the histos after the commit. But, in the osc-16.0 Zebra driver, the "HROUT" is done in fact at the deletion of the tree (and not in the commit() or close()), and then AFTER the histo->reset() in this example, and then the empty histos in the file. I am going to correct that in OSC-16.1, but if someone intends to clone Hadr01 by using OSC-16.0 + HBOOK, he must be aware of this problem. (The best is to comment out the histo[i]->reset() in the Histo::save() method and arrange to use the Histo::reset() at beginOfRun()). From what I have seen, Hadr01 is the only example that does that (reset() the histos after the commit()). Else, anyway the Hadr01/Histo.cc code has to be corrected because the main IAnalysisFactory (the "af" object) is handled by an std::auto_ptr in the Histo::book() and then deleted at end of this method ; and as in OSC, the main analysis factory is the global manager of everything, then the AIDA objects booked in this method will be deleted here too, and then someone will have a crash in later fill() because the objects are no more here ! (I think that the same will happen by using JAIDA/AIDAJNI). If cloning this example, then arrange to create (delete) the "af" in the Histo class constructor (destructor). Else, with the uppers corrected, the example runs nicely and I get a p_pb_20gev.hbook file with no more empty histos that I can plot with CERN/PAW and opaw. Guy Barrand

Re: extended_hadronic_Hadr01 / OpenScientist-16.0 / empty histos in .hbook file by Vladimir IVANTCHENKO <vnivanch@mail.cern.ch>, 24 May, 2007
Re: extended_hadronic_Hadr01 / OpenScientist-16.0 / empty histos in .hbook file (Guy Barrand)

On Thu, 24 May 2007, Guy Barrand wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/285"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Hello > > We have seen, with Jean-Etienne Sauvestre of CEA, that on : > > extended/hadronic/Hadr01 > > of the 8.2, the "hbook" persistency done by using > the Zebra driver of OpenScientist-16.0 > produces a p_pb_20gev.book files with empty histos ! > > This comes from the fact that in this > example (see Histo::save() code), someone do : > > tree->commit(); > tree->close(); > for(G4int i=0; i<nHisto; i++) { > if(histo[i]) histo[i]->reset(); > } > > That is to say, a reset() is done over the > histos after the commit. > > But, in the osc-16.0 Zebra driver, the > "HROUT" is done in fact at the deletion > of the tree (and not in the commit() or close()), > and then AFTER the histo->reset() in this > example, and then the empty histos in the file. > > I am going to correct that in OSC-16.1, but > if someone intends to clone Hadr01 by using > OSC-16.0 + HBOOK, he must be aware of this problem. > (The best is to comment out the histo[i]->reset() > in the Histo::save() method and arrange to > use the Histo::reset() at beginOfRun()). > > From what I have seen, Hadr01 is the only example > that does that (reset() the histos after the commit()). > > Else, anyway the Hadr01/Histo.cc code has to be corrected > because the main IAnalysisFactory (the "af" object) > is handled by an std::auto_ptr in the Histo::book() > and then deleted at end of this method ; and as > in OSC, the main analysis factory is the global manager > of everything, then the AIDA objects booked in > this method will be deleted here too, and then > someone will have a crash in later fill() because > the objects are no more here ! (I think that > the same will happen by using JAIDA/AIDAJNI). > If cloning this example, then arrange to > create (delete) the "af" in the Histo class > constructor (destructor). > > Else, with the uppers corrected, the example > runs nicely and I get a p_pb_20gev.hbook file > with no more empty histos that I can plot > with CERN/PAW and opaw. > > Guy Barrand > Hello Guy, Just today this place was removed from Hadr01 as well as all autopinters... Can you, please, have a look and verify that the commited version is OK? cheers, Vladimir

about installation of OpenScientist Keywords: about installation of OpenScientist by adk <adnank@uludag.edu.tr>, 18 May, 2007 Hello all of the geant4 users, if i use some incorrect expressions by mistake, (in point of programming language), so sorry right now... I and my colleague use Linux OS (Scientific Linux 5 and Ubuntu respectively). I installed Geant4.8.3 version and my collegue installed Geant4.7.1 version on our computers. We have attempt to install the new version of OpenScientist (osc_source_v16r0.zip) to do our data analysis yet, and we try to set up osc_vis kit inside the OpenScientest folder, following the " Build from Source " on OpenScientist web page, but it appears to an error message during compilation ( .sh/build ) like the following: We also meet the same things in case of the other kits except for osc_batch kit. [name @ localhost obuild]$ ./sh/build build obuild/v1r0 ... build foreign/v1r0 ... build zlib/v1r114p3 ... build expat/v1r11p6 ... build Slash/v1r0p0 ... build Lib/v8r0 ... build HCL/v7r0 ... build Midnight/v4r0p0 ... build Minuit/v1r140p4 ... build Rio/v7r1 ... build HDF5/v1r165p2 ... ../src/H5Tconv.c: In function 'H5T_conv_uchar_short': ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:3927: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_uchar_int': ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4056: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_uchar_long': ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4185: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_uchar_llong': ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4317: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_ushort_int': ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4647: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_ushort_long': ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4779: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_ushort_llong': ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:4911: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_uint_llong': ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:5496: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c: In function 'H5T_conv_ulong_llong': ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5Tconv.c:6079: warning: comparison is always false due to limited range of data type ../src/H5V.c: In function 'H5V_hyper_disjointp': ../src/H5V.c:413: warning: comparison is always true due to limited range of data type ../src/H5V.c:414: warning: comparison is always true due to limited range of data type build BatchLab/v1r0 ... build UseAIDA/v1r0p2 ... build osc_source/v16r0 ... build jpeg/v1r62p1 ... build dvi2bitmap/v1r0132p1 ... build freetype2/v1r219p0 ... build CoinGL/v1r244p0 ... ../src/nodes/SoExtSelection.cpp:351: error: extra qualification 'SoExtSelectionP::SelectionState::' on member 'SelectionState' ../src/nodes/SoExtSelection.cpp:359: error: extra qualification 'SoExtSelectionP::SelectionState::' on member 'SelectionState' After these error messages, the process stops itself. Both of us meet the same errors during compilation. Could you please help us what is the problem or what can we do ? yours sincerely. adnan.

Re: about installation of OpenScientist / g++-4.1 Keywords: about installation of OpenScientist by Guy Barrand <Guy Barrand>, 24 May, 2007 Re: about installation of OpenScientist (adk) Hello Then I have put the hand on a g++4.1.0 (by using the g++4 command on CERN/lxplus) and I can reproduce the error in the CoinGL package. In SoExtSelection.cpp, you have to change : line 353: SelectionState::SelectionState(SoExtSelection * t) by : SelectionState(SoExtSelection *t) and : line 361: SelectionState::~SelectionState() by : ~SelectionState() I have modified the code in my repository so that it wil be corrected in OSC-16.1. The code of coin3d-2.4.6 has already the fix. Else, I have done various tests and it seems ok for me. I have added the binary tarball : osc_vis-v16r0-Linux-x86_64-gcc_410.zip under the OSC download area. Regards Guy

Aida and exA01 on x86_64 by Theo <Theo>, 03 May, 2007 Dear all i have suse 10.2 64bit and just installed geant4.after installing jaida and aidajni tried to run example A01 (after compiling it successfully) and got this message which i have no idea what it means. An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x00002b758b0191b6, pid=6235, tid=47783893238560 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03 mixed mode) # Problematic frame: # C [ld-linux-x86-64.so.2+0x91b6] # # An error report file with more information is saved as hs_err_pid6235.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted Any ideas?Thanks in advance. theo

Re: Aida and exA01 on x86_64 by Theo <Theo>, 03 May, 2007 Re: Aida and exA01 on x86_64 (Theo) thanks for the quick reply. well i have used these editions jaida-3.3.0-2-bin.tar.gz and aidajni-3.2.6-amd64-Linux-g++.tar.gz and run aida-config from the folder /aidajni-3.2.6/bin/amd64-Linux-g++ i don't know if tha helps.. thanks again

Re: Aida and exA01 on x86_64 by Theo <Theo>, 04 May, 2007 Re: Re: Aida and exA01 on x86_64 (Theo) i have read somewhere that Java conflicts with openGL, or sth like that.I have set the variable of OpenGL at the installation. Is it possible that this is the case? if so how can i resolve it? thanks again

Re: Aida and exA01 on x86_64 by Mark Donszelmann <Mark Donszelmann>, 04 May, 2007
Re: Re: Aida and exA01 on x86_64 (Theo)

Hi that could still be the case. Try recompiling without OpenGL, or send the full log of your bugreport, so we can inspect it better. Regards Mark On May 4, 2007, at 1:05 PM, theo wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/281/2/1"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > i have read somewhere that Java conflicts with openGL, or sth like > that.I have set the variable of OpenGL at the installation. Is it > possible that this is the case? if so how can i resolve it? thanks > again

Re: Aida and exA01 on x86_64 by Theo <Theo>, 07 May, 2007 Re: Re: Aida and exA01 on x86_64 (Mark Donszelmann) i don't know if that helps but i copy paste the full log report.it's a little bit big.Well here it is: # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x00002b6abb0431b6, pid=10943, tid=47737454076704 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03 mixed mode) # Problematic frame: # C [ld-linux-x86-64.so.2+0x91b6] # --------------- T H R E A D --------------- Current thread (0x00000000011f2d90): JavaThread "main" [_thread_in_native, id=10943] siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x0000000000000000 Registers: RAX=0x0000000000000000, RBX=0x00002b6abb257628, RCX=0x0377cc14b1b73c55, RDX=0x00000000b1b73c55 RSP=0x00007fffefa69b90, RBP=0x00007fffefa69ca0, RSI=0x00002b6abb257628, RDI=0x00002aaaab7bb6be R8 =0x0000000000000000, R9 =0x0000000000000000, R10=0x0000000000000000, R11=0x00000000ffffffff R12=0x0000000000000000, R13=0x00000000b1b73c55, R14=0x00002aaaab7bb6b5, R15=0x0000000000000000 RIP=0x00002b6abb0431b6, EFL=0x0000000000010246, CSGSFS=0x0000000000000033, ERR=0x0000000000000004 TRAPNO=0x000000000000000e Top of Stack: (sp=0x00007fffefa69b90) 0x00007fffefa69b90: 00007fffefa69b90 00002b6ac460d4e0 0x00007fffefa69ba0: 00007fffefa69bd8 00002b6ac469a290 0x00007fffefa69bb0: 0000000000000000 00002b6ac460d4f8 0x00007fffefa69bc0: 00007fffefa69bd8 00007fffefa69c18 0x00007fffefa69bd0: 00002b6ac14d2d36 0000000000000000 0x00007fffefa69be0: 00007fffefa69be0 00000000c460d336 0x00007fffefa69bf0: 0000000000000000 00007fffefa69d00 0x00007fffefa69c00: 00002b6abb257628 00002b6ac460d358 0x00007fffefa69c10: 00007fffefa69c38 00007fffefa69ca0 0x00007fffefa69c20: 00002b6ac14d032d 0000000000000000 0x00007fffefa69c30: 0000000000000000 00002b6ade877060 0x00007fffefa69c40: 0000000000001fa0 00002b6abd476b44 0x00007fffefa69c50: 0000000000000000 0000000000000000 0x00007fffefa69c60: 00002b6abc3a2fbe 00000000ffffffff 0x00007fffefa69c70: 00007fffefa69d10 00002b6abb257628 0x00007fffefa69c80: 0000000000000000 00002b6abb256be0 0x00007fffefa69c90: 00002b6abcbeb1a0 00002aaaac221d60 0x00007fffefa69ca0: 00002aaaab7bb6b5 00002b6abd567d95 0x00007fffefa69cb0: 0000000000000003 0000000000000000 0x00007fffefa69cc0: 00007fffefa69e28 00002b6abd478ac8 0x00007fffefa69cd0: 0000000000000000 00002b6abdddce40 0x00007fffefa69ce0: 00002b6abd0109b0 00002b6abc3a26a4 0x00007fffefa69cf0: 00002b6abd484d80 00002b6abc39f438 0x00007fffefa69d00: 0000000000000000 000000010000003c 0x00007fffefa69d10: 00000000011f2d90 00007fffefa69eb0 0x00007fffefa69d20: 00007fffefa69eb0 00002b6abddde240 0x00007fffefa69d30: 0000000000000007 00002b6abcbeb1a0 0x00007fffefa69d40: 00002aaaac221d60 00002b6abddde254 0x00007fffefa69d50: 0000000000000000 00002b6abb0470c6 0x00007fffefa69d60: 00007fffefa69eb0 00002b6abddde240 0x00007fffefa69d70: 00000000011ef608 00000000011ef618 0x00007fffefa69d80: 00000000011ef610 00002b6abdfe2300 Instructions: (pc=0x00002b6abb0431b6) 0x00002b6abb0431a6: 0f 85 79 03 00 00 48 8b 85 50 ff ff ff 45 31 d2 0x00002b6abb0431b6: 48 8b 10 31 c0 48 85 d2 0f 84 59 03 00 00 48 8b Stack: [0x00007fffef86d000,0x00007fffefa6d000), sp=0x00007fffefa69b90, free space=2034k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [ld-linux-x86-64.so.2+0x91b6] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/String;)V+0 j java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/File;)Z+300 j java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/String;Z)V+217 j java.lang.Runtime.loadLibrary0(Ljava/lang/Class;Ljava/lang/String;)V+54 j java.lang.System.loadLibrary(Ljava/lang/String;)V+7 j sun.security.action.LoadLibraryAction.run()Ljava/lang/Object;+4 v ~StubRoutines::call_stub j java.security.AccessController.doPrivileged(Ljava/security/PrivilegedAction;)Ljava/lang/Object;+0 j sun.nio.ch.Util.load()V+28 j sun.nio.ch.FileChannelImpl.<clinit>()V+29 v ~StubRoutines::call_stub j java.io.RandomAccessFile.getChannel()Ljava/nio/channels/FileChannel;+22 j sun.font.TrueTypeFont.open()Ljava/nio/channels/FileChannel;+30 j sun.font.TrueTypeFont.verify()V+1 j sun.font.TrueTypeFont.<init>(Ljava/lang/String;Ljava/lang/Object;IZ)V+40 j sun.font.FontManager.registerFontFile(Ljava/lang/String;[Ljava/lang/String;IZI)Lsun/font/PhysicalFont;+55 j sun.font.FontManager.initialiseDeferredFont(Ljava/lang/String;)Lsun/font/PhysicalFont;+80 j sun.font.FontManager.initialiseDeferredFonts()V+32 j sun.java2d.SunGraphicsEnvironment.loadFonts()V+30 j sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames(Ljava/util/Locale;)[Ljava/lang/String;+60 j sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames()[Ljava/lang/String;+4 j hep.aida.ref.plotter.FontStyleParameter.<clinit>()V+3 v ~StubRoutines::call_stub j hep.aida.ref.plotter.TextStyle.initializeBaseStyle()V+5 j hep.aida.ref.plotter.BaseStyle.<init>()V+60 j hep.aida.ref.plotter.BrushStyle.<init>()V+1 j hep.aida.ref.plotter.TextStyle.<init>()V+1 j hep.aida.ref.plotter.InfoStyle.initializeBaseStyle()V+5 j hep.aida.ref.plotter.BaseStyle.<init>()V+60 j hep.aida.ref.plotter.InfoStyle.<init>()V+1 j hep.aida.ref.plotter.PlotterStyle.initializeBaseStyle()V+45 j hep.aida.ref.plotter.BaseStyle.<init>()V+60 j hep.aida.ref.plotter.PlotterStyle.<init>()V+1 j hep.aida.ref.plotter.DummyPlotter.<init>(Ljava/lang/String;Ljava/lang/String;)V+53 j hep.aida.ref.plotter.Plotter.<init>(Ljava/lang/String;Ljava/lang/String;)V+3 j hep.aida.ref.plotter.PlotterFactory.create(Ljava/lang/String;Ljava/lang/String;)Lhep/aida/IPlotter;+6 j hep.aida.ref.plotter.PlotterFactory.create(Ljava/lang/String;)Lhep/aida/IPlotter;+3 v ~StubRoutines::call_stub --------------- P R O C E S S --------------- Java Threads: ( => current thread ) 0x00002aaaac245470 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=10955] 0x00000000012db990 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=10953] 0x00000000012d9d60 JavaThread "CompilerThread1" daemon [_thread_in_native, id=10952] 0x00000000012d87b0 JavaThread "CompilerThread0" daemon [_thread_in_native, id=10951] 0x00000000012d7050 JavaThread "AdapterThread" daemon [_thread_in_vm, id=10950] 0x00000000012d5d10 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=10949] 0x00000000012c1310 JavaThread "Finalizer" daemon [_thread_blocked, id=10948] 0x00000000012c0ae0 JavaThread "Reference Handler" daemon [_thread_blocked, id=10947] =>0x00000000011f2d90 JavaThread "main" [_thread_in_native, id=10943] Other Threads: 0x00000000012bc5d0 VMThread [id=10946] 0x00000000012dd5e0 WatcherThread [id=10954] VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None Heap PSYoungGen total 9408K, used 2320K [0x00002b6ade790000, 0x00002b6adf9f0000, 0x00002b6ae8f90000) eden space 8064K, 12% used [0x00002b6ade790000,0x00002b6ade8882d8,0x00002b6adef70000) from space 1344K, 98% used [0x00002b6adef70000,0x00002b6adf0bc030,0x00002b6adf0c0000) to space 1344K, 0% used [0x00002b6adf8a0000,0x00002b6adf8a0000,0x00002b6adf9f0000) PSOldGen total 21504K, used 728K [0x00002b6ac9790000, 0x00002b6acac90000, 0x00002b6ade790000) object space 21504K, 3% used [0x00002b6ac9790000,0x00002b6ac9846018,0x00002b6acac90000) PSPermGen total 21248K, used 5599K [0x00002b6ac4590000, 0x00002b6ac5a50000, 0x00002b6ac9790000) object space 21248K, 26% used [0x00002b6ac4590000,0x00002b6ac4b07d18,0x00002b6ac5a50000) Dynamic libraries: 00400000-00ae9000 r-xp 00000000 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app 00ce9000-00ceb000 r--p 006e9000 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app 00ceb000-00d26000 rw-p 006eb000 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app 00d26000-018cd000 rw-p 00d26000 00:00 0 [heap] 40000000-40001000 ---p 40000000 00:00 0 40001000-40101000 rwxp 40001000 00:00 0 40101000-40102000 ---p 40101000 00:00 0 40102000-40202000 rwxp 40102000 00:00 0 40202000-40203000 ---p 40202000 00:00 0 40203000-40303000 rwxp 40203000 00:00 0 40303000-40306000 ---p 40303000 00:00 0 40306000-40404000 rwxp 40306000 00:00 0 40404000-40407000 ---p 40404000 00:00 0 40407000-40505000 rwxp 40407000 00:00 0 40505000-40508000 ---p 40505000 00:00 0 40508000-40606000 rwxp 40508000 00:00 0 40606000-40609000 ---p 40606000 00:00 0 40609000-40707000 rwxp 40609000 00:00 0 40707000-4070a000 ---p 40707000 00:00 0 4070a000-40808000 rwxp 4070a000 00:00 0 40808000-4080b000 ---p 40808000 00:00 0 4080b000-40909000 rwxp 4080b000 00:00 0 40909000-4090c000 ---p 40909000 00:00 0 4090c000-40a0a000 rwxp 4090c000 00:00 0 40a0a000-40a0b000 ---p 40a0a000 00:00 0 40a0b000-40b0b000 rwxp 40a0b000 00:00 0 40b0b000-40b0e000 ---p 40b0b000 00:00 0 40b0e000-40c0c000 rwxp 40b0e000 00:00 0 2aaaaaaab000-2aaaaaad3000 rw-p 2aaaaaaab000 00:00 0 2aaaaaad3000-2aaaaab0e000 r--p 00000000 08:06 314936 /usr/lib/locale/en_US.utf8/LC_CTYPE 2aaaaab0e000-2aaaaab15000 r--s 00000000 08:06 297966 /usr/lib64/gconv/gconv-modules.cache 2aaaaab15000-2aaaaab17000 r--s 00000000 08:06 493515 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/dnsns.jar 2aaaaab17000-2aaaaabdb000 r--s 00000000 08:06 493516 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/localedata.jar 2aaaaabdb000-2aaaaac02000 r--s 00000000 08:06 493517 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/sunjce_provider.jar 2aaaaac02000-2aaaaac08000 r--s 00000000 08:06 698398 /root/aidajni-3.2.6/lib/freehep-aidajni-3.2.6.jar 2aaaaac08000-2aaaaac14000 r--s 00000000 08:06 730411 /root/jaida-3.3.0-2/lib/optimizers-20020927.jar 2aaaaac14000-2aaaaac24000 r--s 00000000 08:06 730417 /root/jaida-3.3.0-2/lib/openide-lookup-1.9-patched-1.0.jar 2aaaaac24000-2aaaaac93000 r--s 00000000 08:06 730414 /root/jaida-3.3.0-2/lib/l2fprod-common-all-6.9.1.jar 2aaaaac93000-2aaaaacb1000 r--s 00000000 08:06 730403 /root/jaida-3.3.0-2/lib/junit-3.8.2.jar 2aaaaacb1000-2aaaaacba000 r--s 00000000 08:06 730395 /root/jaida-3.3.0-2/lib/jel-0.9.10.jar 2aaaaacba000-2aaaaace0000 r--s 00000000 08:06 730404 /root/jaida-3.3.0-2/lib/jdom-1.0.jar 2aaaaace0000-2aaaaad91000 r--s 00000000 08:06 730392 /root/jaida-3.3.0-2/lib/jas-plotter-2.1.jar 2aaaaad91000-2aaaaadb7000 r--s 00000000 08:06 730412 /root/jaida-3.3.0-2/lib/freehep-xml-2.0.1.jar 2aaaaadb7000-2aaaaadc4000 r--s 00000000 08:06 730393 /root/jaida-3.3.0-2/lib/freehep-util-2.0.1.jar 2aaaaadc4000-2aaaaadf9000 r--s 00000000 08:06 730428 /root/jaida-3.3.0-2/lib/freehep-swing-2.0.2.jar 2aaaaadf9000-2aaaaae3c000 r--s 00000000 08:06 730402 /root/jaida-3.3.0-2/lib/freehep-rootio-2.0.jar 2aaaaae3c000-2aaaaaeba000 r--s 00000000 08:06 730425 /root/jaida-3.3.0-2/lib/bcel-5.1.jar 2aaaaaeba000-2aaaaaed9000 r--s 00000000 08:06 730423 /root/jaida-3.3.0-2/lib/freehep-jminuit-jdk1.4-1.0.jar 2aaaaaed9000-2aaaaaee1000 r--s 00000000 08:06 730408 /root/jaida-3.3.0-2/lib/freehep-jaida-root-3.3.0-2.jar 2aaaaaee1000-2aaaaaf27000 r--s 00000000 08:06 730429 /root/jaida-3.3.0-2/lib/freehep-jaida-remote-3.3.0-2.jar 2aaaaaf27000-2aaaaaf2a000 r--s 00000000 08:06 730401 /root/jaida-3.3.0-2/lib/freehep-jaida-jminuit-3.3.0-2.jar 2aaaaaf2a000-2aaaaaf2e000 r--s 00000000 08:06 730415 /root/jaida-3.3.0-2/lib/freehep-jaida-hbook-3.3.0-2.jar 2aaaaaf2e000-2aaaaaf32000 r--s 00000000 08:06 730421 /root/jaida-3.3.0-2/lib/freehep-jaida-fminuit-3.3.0-2.jar 2aaaaaf32000-2aaaab002000 r--s 00000000 08:06 730424 /root/jaida-3.3.0-2/lib/freehep-jaida-3.3.0-2.jar 2aaaab002000-2aaaab012000 r--s 00000000 08:06 730427 /root/jaida-3.3.0-2/lib/freehep-io-2.0.1.jar 2aaaab012000-2aaaab01a000 r--s 00000000 08:06 730394 /root/jaida-3.3.0-2/lib/freehep-hbook-2.0.jar 2aaaab01a000-2aaaab047000 r--s 00000000 08:06 730398 /root/jaida-3.3.0-2/lib/freehep-graphicsio-swf-2.0.jar 2aaaab047000-2aaaab04d000 r--s 00000000 08:06 730410 /root/jaida-3.3.0-2/lib/freehep-graphicsio-svg-2.0.jar 2aaaab04d000-2aaaab059000 r--s 00000000 08:06 730420 /root/jaida-3.3.0-2/lib/freehep-graphicsio-ps-2.0.jar 2aaaab059000-2aaaab06c000 r--s 00000000 08:06 730399 /root/jaida-3.3.0-2/lib/freehep-graphicsio-pdf-2.0.jar 2aaaab06c000-2aaaab08f000 r--s 00000000 08:06 730422 /root/jaida-3.3.0-2/lib/freehep-graphicsio-emf-2.0.jar 2aaaab08f000-2aaaab0bd000 r--s 00000000 08:06 730409 /root/jaida-3.3.0-2/lib/freehep-graphicsio-2.0.jar 2aaaab0bd000-2aaaab0db000 r--s 00000000 08:06 730400 /root/jaida-3.3.0-2/lib/freehep-graphics2d-2.0.jar 2aaaab0db000-2aaaab0dd000 r--s 00000000 08:06 730406 /root/jaida-3.3.0-2/lib/freehep-fminuit-2.0.jar 2aaaab0dd000-2aaaab0e2000 r--s 00000000 08:06 730396 /root/jaida-3.3.0-2/lib/freehep-export-2.0.3.jar 2aaaab0e2000-2aaaab113000 r--s 00000000 08:06 730416 /root/jaida-3.3.0-2/lib/freehep-application-2.0.jar 2aaaab113000-2aaaab114000 r--s 00000000 08:06 730426 /root/jaida-3.3.0-2/lib/fortran-1.0.jar 2aaaab114000-2aaaab13f000 r--s 00000000 08:06 730407 /root/jaida-3.3.0-2/lib/commons-math-1.1.jar 2aaaab13f000-2aaaab147000 r--s 00000000 08:06 730413 /root/jaida-3.3.0-2/lib/commons-logging-1.0.3.jar 2aaaab147000-2aaaab159000 r--s 00000000 08:06 730397 /root/jaida-3.3.0-2/lib/commons-discovery-0.2.jar 2aaaab159000-2aaaab15a000 r--s 00000000 08:06 730419 /root/jaida-3.3.0-2/lib/cernlib-2003-1.0.1.jar 2aaaab15a000-2aaaab15b000 r--s 00000000 08:06 730418 /root/jaida-3.3.0-2/lib/aida-dev-3.3.jar 2aaaab15b000-2aaaab166000 r--s 00000000 08:06 730405 /root/jaida-3.3.0-2/lib/aida-3.3.jar 2aaaab166000-2aaaab1d3000 r-xp 00000000 08:06 493465 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so 2aaaab1d3000-2aaaab2d6000 ---p 0006d000 08:06 493465 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so 2aaaab2d6000-2aaaab2ea000 rw-p 00070000 08:06 493465 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so 2aaaab2ea000-2aaaab30e000 rw-p 2aaaab2ea000 00:00 0 2aaaab30e000-2aaaab3b8000 r-xp 00000000 08:06 493482 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libmlib_image.so 2aaaab3b8000-2aaaab4b7000 ---p 000aa000 08:06 493482 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libmlib_image.so 2aaaab4b7000-2aaaab4bc000 rw-p 000a9000 08:06 493482 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libmlib_image.so 2aaaab4bc000-2aaaab4ee000 r-xp 00000000 08:06 493500 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/libmawt.so 2aaaab4ee000-2aaaab5f0000 ---p 00032000 08:06 493500 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/libmawt.so 2aaaab5f0000-2aaaab5fb000 rw-p 00034000 08:06 493500 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/libmawt.so 2aaaab5fb000-2aaaab5fc000 rw-p 2aaaab5fb000 00:00 0 2aaaab5fc000-2aaaab678000 r-xp 00000000 08:06 493469 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libfontmanager.so 2aaaab678000-2aaaab778000 ---p 0007c000 08:06 493469 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libfontmanager.so 2aaaab778000-2aaaab78e000 rw-p 0007c000 08:06 493469 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libfontmanager.so 2aaaab78e000-2aaaab79f000 rw-p 2aaaab78e000 00:00 0 2aaaab79f000-2aaaab7a0000 r--s 00000000 08:06 1083777 /var/cache/fontconfig/cf6c88e680607f2ab796171745f068a4-x86-64.cache-2 2aaaab7a0000-2aaaab7a3000 r--s 00000000 08:06 1083775 /var/cache/fontconfig/d458be102e54cf534d1eef0dcbb02d07-x86-64.cache-2 2aaaab7a3000-2aaaab7aa000 r--s 00000000 08:06 1083768 /var/cache/fontconfig/d62e99ef547d1d24cdb1bd22ec1a2976-x86-64.cache-2 2aaaab7aa000-2aaaab7bc000 r-xp 00000000 08:06 493484 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so 2aaaab7bc000-2aaaab8be000 ---p 00012000 08:06 493484 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so 2aaaab8be000-2aaaab8c1000 rw-p 00014000 08:06 493484 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so 2aaaabe9b000-2aaaabecb000 r--s 00000000 08:06 1083773 /var/cache/fontconfig/8d4af663993b81a124ee82e610bb31f9-x86-64.cache-2 2aaaabecb000-2aaaabf30000 r--s 00000000 08:06 1083765 /var/cache/fontconfig/df311e82a1a24c41a75c2c930223552e-x86-64.cache-2 2aaaabf30000-2aaaabf95000 r--s 00000000 08:06 1083766 /var/cache/fontconfig/17090aa38d5c6f09fb8c5c354938f1d7-x86-64.cache-2 2aaaac000000-2aaaac2ce000 rw-p 2aaaac000000 00:00 0 2aaaac2ce000-2aaab0000000 ---p 2aaaac2ce000 00:00 0 2aaab0224000-2aaab0294000 r--s 00000000 08:06 1083774 /var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-x86-64.cache-2 2aaab0294000-2aaab0295000 r--s 00000000 08:06 1083780 /var/cache/fontconfig/b6bbb9f898b73777cfe763014a8c08d3-x86-64.cache-2 2aaab0295000-2aaab0298000 r--s 00000000 08:06 1083781 /var/cache/fontconfig/6307940f96b0234967c0dcf48f992dfa-x86-64.cache-2 2aaab0298000-2aaab029e000 r--s 00000000 08:06 1083782 /var/cache/fontconfig/e7a9aeb6c664d7354b888275e57aa4d9-x86-64.cache-2 2aaab029e000-2aaab02a8000 r--s 00000000 08:06 1083769 /var/cache/fontconfig/77e41c5059666d75f92e318d4be8c21e-x86-64.cache-2 2b6abb03a000-2b6abb056000 r-xp 00000000 08:06 851970 /lib64/ld-2.5.so 2b6abb056000-2b6abb058000 rw-p 2b6abb056000 00:00 0 2b6abb058000-2b6abb059000 r--p 2b6abb058000 00:00 0 2b6abb059000-2b6abb05a000 rwxp 2b6abb059000 00:00 0 2b6abb08f000-2b6abb090000 rw-p 2b6abb08f000 00:00 0 2b6abb090000-2b6abb099000 r-xp 00000000 08:06 493494 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/native_threads/libhpi.so 2b6abb099000-2b6abb198000 ---p 00009000 08:06 493494 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/native_threads/libhpi.so 2b6abb198000-2b6abb19c000 rw-p 00008000 08:06 493494 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/native_threads/libhpi.so 2b6abb19c000-2b6abb1d1000 r--s 00000000 08:06 1084039 /var/run/nscd/passwd 2b6abb1d1000-2b6abb1d9000 rw-s 00000000 08:06 51208 /tmp/hsperfdata_root/10943 2b6abb256000-2b6abb258000 rw-p 0001c000 08:06 851970 /lib64/ld-2.5.so 2b6abb258000-2b6abb26f000 r-xp 00000000 08:06 508048 /usr/lib64/libXmu.so.6.2.0 2b6abb26f000-2b6abb46f000 ---p 00017000 08:06 508048 /usr/lib64/libXmu.so.6.2.0 2b6abb46f000-2b6abb471000 rw-p 00017000 08:06 508048 /usr/lib64/libXmu.so.6.2.0 2b6abb471000-2b6abb4cc000 r-xp 00000000 08:06 507918 /usr/lib64/libXt.so.6.0.0 2b6abb4cc000-2b6abb6cc000 ---p 0005b000 08:06 507918 /usr/lib64/libXt.so.6.0.0 2b6abb6cc000-2b6abb6d2000 rw-p 0005b000 08:06 507918 /usr/lib64/libXt.so.6.0.0 2b6abb6d2000-2b6abb6d3000 rw-p 2b6abb6d2000 00:00 0 2b6abb6d3000-2b6abb6e3000 r-xp 00000000 08:06 507912 /usr/lib64/libXext.so.6.4.0 2b6abb6e3000-2b6abb8e2000 ---p 00010000 08:06 507912 /usr/lib64/libXext.so.6.4.0 2b6abb8e2000-2b6abb8e4000 rw-p 0000f000 08:06 507912 /usr/lib64/libXext.so.6.4.0 2b6abb8e4000-2b6abb8e5000 rw-p 2b6abb8e4000 00:00 0 2b6abb8e5000-2b6abba17000 r-xp 00000000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abba17000-2b6abbc17000 ---p 00132000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abbc17000-2b6abbc18000 r--p 00132000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abbc18000-2b6abbc1f000 rw-p 00133000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abbc1f000-2b6abbc28000 r-xp 00000000 08:06 217931 /usr/lib64/libSM.so.6.0.0 2b6abbc28000-2b6abbe28000 ---p 00009000 08:06 217931 /usr/lib64/libSM.so.6.0.0 2b6abbe28000-2b6abbe2a000 rw-p 00009000 08:06 217931 /usr/lib64/libSM.so.6.0.0 2b6abbe2a000-2b6abbe41000 r-xp 00000000 08:06 216934 /usr/lib64/libICE.so.6.3.0 2b6abbe41000-2b6abc040000 ---p 00017000 08:06 216934 /usr/lib64/libICE.so.6.3.0 2b6abc040000-2b6abc042000 rw-p 00016000 08:06 216934 /usr/lib64/libICE.so.6.3.0 2b6abc042000-2b6abc047000 rw-p 2b6abc042000 00:00 0 2b6abc047000-2b6abc193000 r-xp 00000000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc193000-2b6abc393000 ---p 0014c000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc393000-2b6abc399000 r--p 0014c000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc399000-2b6abc39b000 rw-p 00152000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc39b000-2b6abc39e000 rw-p 2b6abc39b000 00:00 0 2b6abc39e000-2b6abca69000 r-xp 00000000 08:06 493498 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/libjvm.so 2b6abca69000-2b6abcb68000 ---p 006cb000 08:06 493498 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/libjvm.so 2b6abcb68000-2b6abcce3000 rw-p 006ca000 08:06 493498 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/libjvm.so 2b6abcce3000-2b6abcd12000 rw-p 2b6abcce3000 00:00 0 2b6abcd12000-2b6abcdf5000 r-xp 00000000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcdf5000-2b6abcff5000 ---p 000e3000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcff5000-2b6abcffb000 r--p 000e3000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcffb000-2b6abcffe000 rw-p 000e9000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcffe000-2b6abd011000 rw-p 2b6abcffe000 00:00 0 2b6abd011000-2b6abd066000 r-xp 00000000 08:06 851985 /lib64/libm-2.5.so 2b6abd066000-2b6abd265000 ---p 00055000 08:06 851985 /lib64/libm-2.5.so 2b6abd265000-2b6abd267000 rw-p 00054000 08:06 851985 /lib64/libm-2.5.so 2b6abd267000-2b6abd274000 r-xp 00000000 08:06 852021 /lib64/libgcc_s.so.1 2b6abd274000-2b6abd473000 ---p 0000d000 08:06 852021 /lib64/libgcc_s.so.1 2b6abd473000-2b6abd475000 rw-p 0000c000 08:06 852021 /lib64/libgcc_s.so.1 2b6abd475000-2b6abd5ae000 r-xp 00000000 08:06 851977 /lib64/libc-2.5.so 2b6abd5ae000-2b6abd7ad000 ---p 00139000 08:06 851977 /lib64/libc-2.5.so 2b6abd7ad000-2b6abd7b0000 r--p 00138000 08:06 851977 /lib64/libc-2.5.so 2b6abd7b0000-2b6abd7b2000 rw-p 0013b000 08:06 851977 /lib64/libc-2.5.so 2b6abd7b2000-2b6abd7b8000 rw-p 2b6abd7b2000 00:00 0 2b6abd7b8000-2b6abd7bd000 r-xp 00000000 08:06 216938 /usr/lib64/libXdmcp.so.6.0.0 2b6abd7bd000-2b6abd9bc000 ---p 00005000 08:06 216938 /usr/lib64/libXdmcp.so.6.0.0 2b6abd9bc000-2b6abd9be000 rw-p 00004000 08:06 216938 /usr/lib64/libXdmcp.so.6.0.0 2b6abd9be000-2b6abd9d4000 r-xp 00000000 08:06 852003 /lib64/libpthread-2.5.so 2b6abd9d4000-2b6abdbd3000 ---p 00016000 08:06 852003 /lib64/libpthread-2.5.so 2b6abdbd3000-2b6abdbd5000 rw-p 00015000 08:06 852003 /lib64/libpthread-2.5.so 2b6abdbd5000-2b6abdbd9000 rw-p 2b6abdbd5000 00:00 0 2b6abdbd9000-2b6abdbdb000 r-xp 00000000 08:06 216936 /usr/lib64/libXau.so.6.0.0 2b6abdbdb000-2b6abddda000 ---p 00002000 08:06 216936 /usr/lib64/libXau.so.6.0.0 2b6abddda000-2b6abdddc000 rw-p 00001000 08:06 216936 /usr/lib64/libXau.so.6.0.0 2b6abdddc000-2b6abdddd000 rw-p 2b6abdddc000 00:00 0 2b6abdddd000-2b6abdddf000 r-xp 00000000 08:06 851983 /lib64/libdl-2.5.so 2b6abdddf000-2b6abdfdf000 ---p 00002000 08:06 851983 /lib64/libdl-2.5.so 2b6abdfdf000-2b6abdfe1000 rw-p 00002000 08:06 851983 /lib64/libdl-2.5.so 2b6abdfe1000-2b6abdfe3000 rw-p 2b6abdfe1000 00:00 0 2b6abdfe3000-2b6abdff7000 r-xp 00000000 08:06 851988 /lib64/libnsl-2.5.so 2b6abdff7000-2b6abe1f6000 ---p 00014000 08:06 851988 /lib64/libnsl-2.5.so 2b6abe1f6000-2b6abe1f8000 rw-p 00013000 08:06 851988 /lib64/libnsl-2.5.so 2b6abe1f8000-2b6abe1fa000 rw-p 2b6abe1f8000 00:00 0 2b6abe1fa000-2b6abe207000 r-xp 00000000 08:06 493489 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so 2b6abe207000-2b6abe306000 ---p 0000d000 08:06 493489 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so 2b6abe306000-2b6abe309000 rw-p 0000c000 08:06 493489 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so 2b6abe309000-2b6abe32e000 r-xp 00000000 08:06 493474 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so 2b6abe32e000-2b6abe42d000 ---p 00025000 08:06 493474 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so 2b6abe42d000-2b6abe433000 rw-p 00024000 08:06 493474 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so 2b6abe433000-2b6abe442000 r-xp 00000000 08:06 493490 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so 2b6abe442000-2b6abe543000 ---p 0000f000 08:06 493490 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so 2b6abe543000-2b6abe547000 rw-p 00010000 08:06 493490 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so 2b6abe547000-2b6ac0b5d000 r--s 00000000 08:06 493583 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/rt.jar 2b6ac0b5d000-2b6ac0bc6000 rw-p 2b6ac0b5d000 00:00 0 2b6ac0bc6000-2b6ac0c4b000 r--s 00000000 08:06 493566 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/jsse.jar 2b6ac0c4b000-2b6ac0c60000 r--s 00000000 08:06 493565 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/jce.jar 2b6ac0c60000-2b6ac14d0000 r--s 00000000 08:06 493504 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/charsets.jar 2b6ac14d0000-2b6ac1740000 rwxp 2b6ac14d0000 00:00 0 2b6ac1740000-2b6ac44d0000 rwxp 2b6ac1740000 00:00 0 2b6ac44d0000-2b6ac44da000 rwxp 2b6ac44d0000 00:00 0 2b6ac44da000-2b6ac4590000 rwxp 2b6ac44da000 00:00 0 2b6ac4590000-2b6ac5a50000 rwxp 2b6ac4590000 00:00 0 2b6ac5a50000-2b6ac9790000 rwxp 2b6ac5a50000 00:00 0 2b6ac9790000-2b6acac90000 rwxp 2b6ac9790000 00:00 0 2b6acac90000-2b6ade790000 rwxp 2b6acac90000 00:00 0 2b6ade790000-2b6adf9f0000 rwxp 2b6ade790000 00:00 0 2b6adf9f0000-2b6ae8f90000 rwxp 2b6adf9f0000 00:00 0 2b6ae8f90000-2b6ae8f9b000 rwxp 2b6ae8f90000 00:00 0 2b6ae8f9b000-2b6ae8fb9000 rwxp 2b6ae8f9b000 00:00 0 2b6ae8fb9000-2b6ae8fc4000 rwxp 2b6ae8fb9000 00:00 0 2b6ae8fc4000-2b6ae9061000 rwxp 2b6ae8fc4000 00:00 0 2b6ae9061000-2b6ae906b000 rwxp 2b6ae9061000 00:00 0 2b6ae906b000-2b6ae90b5000 rwxp 2b6ae906b000 00:00 0 2b6ae90b5000-2b6ae90c1000 rwxp 2b6ae90b5000 00:00 0 2b6ae90c1000-2b6ae915e000 rwxp 2b6ae90c1000 00:00 0 2b6ae915e000-2b6ae9169000 rwxp 2b6ae915e000 00:00 0 2b6ae9169000-2b6ae9187000 rwxp 2b6ae9169000 00:00 0 7fffef86d000-7fffef870000 ---p 7fffef86d000 00:00 0 7fffef870000-7fffefa6d000 rwxp 7fffef870000 00:00 0 [stack] 7fffefa6d000-7fffefa70000 rw-p 7fffefa6d000 00:00 0 ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso] VM Arguments: java_command: <unknown> Launcher Type: generic Environment Variables: JAVA_HOME=/usr/lib64/jvm/java JRE_HOME=/usr/lib64/jvm/java/jre PATH=/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/aidajni-3.2.6/bin/amd64-Linux-g++:/sbin:/usr/sbin:/usr/local/sbin:/opt/kde3/sbin:/opt/gnome/sbin:/root/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/lib/qt3/bin:/home/G4Workdir/bin/Linux-g++:/home/G4Workdir/bin/Linux-g++:/home/G4Workdir/bin/Linux-g++ LD_LIBRARY_PATH=/usr/lib64/jvm/java/jre/lib/amd64:/usr/lib64/jvm/java/jre/lib/amd64/server:/root/aidajni-3.2.6/lib/amd64-Linux-g++:/root/2.0.3.1/CLHEP SHELL=/bin/bash DISPLAY=:0.0 HOSTTYPE=x86_64 OSTYPE=linux MACHTYPE=x86_64-suse-linux Signal Handlers: SIGSEGV: [libjvm.so+0x656380], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGBUS: [libjvm.so+0x656380], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGFPE: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGPIPE: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGILL: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGUSR1: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000 SIGUSR2: [libjvm.so+0x55fc00], sa_mask[0]=0x00000000, sa_flags=0x14000004 SIGHUP: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGINT: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGQUIT: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGTERM: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 --------------- S Y S T E M --------------- OS:openSUSE 10.2 (X86-64) VERSION = 10.2 uname:Linux 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 x86_64 libc:glibc 2.5 NPTL 2.5 rlimit: STACK 8192k, CORE 0k, NPROC 16382, NOFILE 8192, AS 2882320k load average:0.41 0.27 0.20 CPU:total 2 em64t ht Memory: 4k page, physical 2060636k(907992k free), swap 1542200k(1542200k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03) for linux-amd64, built on Jun 28 2006 00:27:03 by java_re with gcc 3.2.2 (SuSE Linux)

Re: Aida and exA01 on x86_64 by Mark Donszelmann <Mark Donszelmann>, 15 May, 2007
Re: Re: Aida and exA01 on x86_64 (Theo)

Hi Theo, looking more closely at your output log it looks to me that our call from JAIDA plotter to java's getAvailableFontFamilyNames is failing. Question, are you running with a proper XWindows DISPLAY set, that is can you open an xterm from the same session and see that display. If so, then I wonder what is wrong. If not, then make sure you can, otherwise the example cannot open a window to show its output. The other things which may be wrong is the java installation itself. Are you sure you run with the 64 bit version of Java? Regards Mark Donszelmann On May 7, 2007, at 10:11 AM, theo wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/281/2/1/1/4"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > i don't know if that helps but i copy paste the full log report.it's a > little bit big.Well here it is: > > # > # An unexpected error has been detected by HotSpot Virtual Machine: > # > # SIGSEGV (0xb) at pc=0x00002b6abb0431b6, pid=10943, > tid=47737454076704 > # > # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03 mixed mode) > # Problematic frame: > # C [ld-linux-x86-64.so.2+0x91b6] > # > > --------------- T H R E A D --------------- > > Current thread (0x00000000011f2d90): JavaThread "main" > [_thread_in_native, id=10943] > > siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x0000000000000000 > > Registers: > RAX=0x0000000000000000, RBX=0x00002b6abb257628, > RCX=0x0377cc14b1b73c55, RDX=0x00000000b1b73c55 > RSP=0x00007fffefa69b90, RBP=0x00007fffefa69ca0, > RSI=0x00002b6abb257628, RDI=0x00002aaaab7bb6be > R8 =0x0000000000000000, R9 =0x0000000000000000, > R10=0x0000000000000000, R11=0x00000000ffffffff > R12=0x0000000000000000, R13=0x00000000b1b73c55, > R14=0x00002aaaab7bb6b5, R15=0x0000000000000000 > RIP=0x00002b6abb0431b6, EFL=0x0000000000010246, > CSGSFS=0x0000000000000033, ERR=0x0000000000000004 > TRAPNO=0x000000000000000e > > Top of Stack: (sp=0x00007fffefa69b90) > > 0x00007fffefa69b90: 00007fffefa69b90 00002b6ac460d4e0 > 0x00007fffefa69ba0: 00007fffefa69bd8 00002b6ac469a290 > 0x00007fffefa69bb0: 0000000000000000 00002b6ac460d4f8 > 0x00007fffefa69bc0: 00007fffefa69bd8 00007fffefa69c18 > 0x00007fffefa69bd0: 00002b6ac14d2d36 0000000000000000 > 0x00007fffefa69be0: 00007fffefa69be0 00000000c460d336 > 0x00007fffefa69bf0: 0000000000000000 00007fffefa69d00 > 0x00007fffefa69c00: 00002b6abb257628 00002b6ac460d358 > 0x00007fffefa69c10: 00007fffefa69c38 00007fffefa69ca0 > 0x00007fffefa69c20: 00002b6ac14d032d 0000000000000000 > 0x00007fffefa69c30: 0000000000000000 00002b6ade877060 > 0x00007fffefa69c40: 0000000000001fa0 00002b6abd476b44 > 0x00007fffefa69c50: 0000000000000000 0000000000000000 > 0x00007fffefa69c60: 00002b6abc3a2fbe 00000000ffffffff > 0x00007fffefa69c70: 00007fffefa69d10 00002b6abb257628 > 0x00007fffefa69c80: 0000000000000000 00002b6abb256be0 > 0x00007fffefa69c90: 00002b6abcbeb1a0 00002aaaac221d60 > 0x00007fffefa69ca0: 00002aaaab7bb6b5 00002b6abd567d95 > 0x00007fffefa69cb0: 0000000000000003 0000000000000000 > 0x00007fffefa69cc0: 00007fffefa69e28 00002b6abd478ac8 > 0x00007fffefa69cd0: 0000000000000000 00002b6abdddce40 > 0x00007fffefa69ce0: 00002b6abd0109b0 00002b6abc3a26a4 > 0x00007fffefa69cf0: 00002b6abd484d80 00002b6abc39f438 > 0x00007fffefa69d00: 0000000000000000 000000010000003c > 0x00007fffefa69d10: 00000000011f2d90 00007fffefa69eb0 > 0x00007fffefa69d20: 00007fffefa69eb0 00002b6abddde240 > 0x00007fffefa69d30: 0000000000000007 00002b6abcbeb1a0 > 0x00007fffefa69d40: 00002aaaac221d60 00002b6abddde254 > 0x00007fffefa69d50: 0000000000000000 00002b6abb0470c6 > 0x00007fffefa69d60: 00007fffefa69eb0 00002b6abddde240 > 0x00007fffefa69d70: 00000000011ef608 00000000011ef618 > 0x00007fffefa69d80: 00000000011ef610 00002b6abdfe2300 > > Instructions: (pc=0x00002b6abb0431b6) > 0x00002b6abb0431a6: 0f 85 79 03 00 00 48 8b 85 50 ff ff ff 45 31 d2 > 0x00002b6abb0431b6: 48 8b 10 31 c0 48 85 d2 0f 84 59 03 00 00 48 8b > > Stack: [0x00007fffef86d000,0x00007fffefa6d000), > sp=0x00007fffefa69b90, free space=2034k > > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, > C=native code) C [ld-linux-x86-64.so.2+0x91b6] > > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j > java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/String;)V+0 j > java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/File;)Z > +300 > j > java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/ > String;Z)V+217 > j > java.lang.Runtime.loadLibrary0(Ljava/lang/Class;Ljava/lang/String;)V > +54 > j java.lang.System.loadLibrary(Ljava/lang/String;)V+7 j > sun.security.action.LoadLibraryAction.run()Ljava/lang/Object;+4 v > ~StubRoutines::call_stub j > java.security.AccessController.doPrivileged(Ljava/security/ > PrivilegedAction;)Ljava/lang/Object;+0 > j sun.nio.ch.Util.load()V+28 j sun.nio.ch.FileChannelImpl.<clinit>() > V+29 > v ~StubRoutines::call_stub j > java.io.RandomAccessFile.getChannel()Ljava/nio/channels/FileChannel; > +22 > j sun.font.TrueTypeFont.open()Ljava/nio/channels/FileChannel;+30 j > sun.font.TrueTypeFont.verify()V+1 j > sun.font.TrueTypeFont.<init>(Ljava/lang/String;Ljava/lang/Object;IZ) > V+40 > j > sun.font.FontManager.registerFontFile(Ljava/lang/String;[Ljava/lang/ > String;IZI)Lsun/font/PhysicalFont;+55 > j > sun.font.FontManager.initialiseDeferredFont(Ljava/lang/String;)Lsun/ > font/PhysicalFont;+80 > j sun.font.FontManager.initialiseDeferredFonts()V+32 j > sun.java2d.SunGraphicsEnvironment.loadFonts()V+30 j > sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames(Ljava/ > util/Locale;)[Ljava/lang/String;+60 > j > sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames() > [Ljava/lang/String;+4 > j hep.aida.ref.plotter.FontStyleParameter.<clinit>()V+3 v > ~StubRoutines::call_stub j > hep.aida.ref.plotter.TextStyle.initializeBaseStyle()V+5 j > hep.aida.ref.plotter.BaseStyle.<init>()V+60 j > hep.aida.ref.plotter.BrushStyle.<init>()V+1 j > hep.aida.ref.plotter.TextStyle.<init>()V+1 j > hep.aida.ref.plotter.InfoStyle.initializeBaseStyle()V+5 j > hep.aida.ref.plotter.BaseStyle.<init>()V+60 j > hep.aida.ref.plotter.InfoStyle.<init>()V+1 j > hep.aida.ref.plotter.PlotterStyle.initializeBaseStyle()V+45 j > hep.aida.ref.plotter.BaseStyle.<init>()V+60 j > hep.aida.ref.plotter.PlotterStyle.<init>()V+1 j > hep.aida.ref.plotter.DummyPlotter.<init>(Ljava/lang/String;Ljava/ > lang/String;)V+53 > j > hep.aida.ref.plotter.Plotter.<init>(Ljava/lang/String;Ljava/lang/ > String;)V+3 > j > hep.aida.ref.plotter.PlotterFactory.create(Ljava/lang/String;Ljava/ > lang/String;)Lhep/aida/IPlotter;+6 > j > hep.aida.ref.plotter.PlotterFactory.create(Ljava/lang/String;)Lhep/ > aida/IPlotter;+3 > v ~StubRoutines::call_stub > > --------------- P R O C E S S --------------- > > Java Threads: ( => current thread ) > 0x00002aaaac245470 JavaThread "Java2D Disposer" daemon > [_thread_blocked, id=10955] > 0x00000000012db990 JavaThread "Low Memory Detector" daemon > [_thread_blocked, id=10953] > 0x00000000012d9d60 JavaThread "CompilerThread1" daemon > [_thread_in_native, id=10952] > 0x00000000012d87b0 JavaThread "CompilerThread0" daemon > [_thread_in_native, id=10951] > 0x00000000012d7050 JavaThread "AdapterThread" daemon > [_thread_in_vm, id=10950] > 0x00000000012d5d10 JavaThread "Signal Dispatcher" daemon > [_thread_blocked, id=10949] > 0x00000000012c1310 JavaThread "Finalizer" daemon > [_thread_blocked, id=10948] > 0x00000000012c0ae0 JavaThread "Reference Handler" daemon > [_thread_blocked, id=10947] > =>0x00000000011f2d90 JavaThread "main" [_thread_in_native, id=10943] > > Other Threads: > 0x00000000012bc5d0 VMThread [id=10946] > 0x00000000012dd5e0 WatcherThread [id=10954] > > VM state:not at safepoint (normal execution) > > VM Mutex/Monitor currently owned by a thread: None > > Heap > PSYoungGen total 9408K, used 2320K [0x00002b6ade790000, > 0x00002b6adf9f0000, 0x00002b6ae8f90000) > eden space 8064K, 12% used > [0x00002b6ade790000,0x00002b6ade8882d8,0x00002b6adef70000) > from space 1344K, 98% used > [0x00002b6adef70000,0x00002b6adf0bc030,0x00002b6adf0c0000) > to space 1344K, 0% used > [0x00002b6adf8a0000,0x00002b6adf8a0000,0x00002b6adf9f0000) > PSOldGen total 21504K, used 728K [0x00002b6ac9790000, > 0x00002b6acac90000, 0x00002b6ade790000) > object space 21504K, 3% used > [0x00002b6ac9790000,0x00002b6ac9846018,0x00002b6acac90000) > PSPermGen total 21248K, used 5599K [0x00002b6ac4590000, > 0x00002b6ac5a50000, 0x00002b6ac9790000) > object space 21248K, 26% used > [0x00002b6ac4590000,0x00002b6ac4b07d18,0x00002b6ac5a50000) > > Dynamic libraries: 00400000-00ae9000 r-xp 00000000 08:07 1458305 > /home/G4Workdir/bin/Linux-g++/A01app 00ce9000-00ceb000 r--p 006e9000 > 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app 00ceb000-00d26000 > rw-p 006eb000 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app > 00d26000-018cd000 rw-p 00d26000 00:00 0 [heap] 40000000-40001000 ---p > 40000000 00:00 0 40001000-40101000 rwxp 40001000 00:00 0 > 40101000-40102000 ---p 40101000 00:00 0 40102000-40202000 rwxp > 40102000 > 00:00 0 40202000-40203000 ---p 40202000 00:00 0 40203000-40303000 rwxp > 40203000 00:00 0 40303000-40306000 ---p 40303000 00:00 0 > 40306000-40404000 rwxp 40306000 00:00 0 40404000-40407000 ---p > 40404000 > 00:00 0 40407000-40505000 rwxp 40407000 00:00 0 40505000-40508000 ---p > 40505000 00:00 0 40508000-40606000 rwxp 40508000 00:00 0 > 40606000-40609000 ---p 40606000 00:00 0 40609000-40707000 rwxp > 40609000 > 00:00 0 40707000-4070a000 ---p 40707000 00:00 0 4070a000-40808000 rwxp > 4070a000 00:00 0 40808000-4080b000 ---p 40808000 00:00 0 > 4080b000-40909000 rwxp 4080b000 00:00 0 40909000-4090c000 ---p > 40909000 > 00:00 0 4090c000-40a0a000 rwxp 4090c000 00:00 0 40a0a000-40a0b000 ---p > 40a0a000 00:00 0 40a0b000-40b0b000 rwxp 40a0b000 00:00 0 > 40b0b000-40b0e000 ---p 40b0b000 00:00 0 40b0e000-40c0c000 rwxp > 40b0e000 > 00:00 0 2aaaaaaab000-2aaaaaad3000 rw-p 2aaaaaaab000 00:00 0 > 2aaaaaad3000-2aaaaab0e000 r--p 00000000 08:06 314936 > /usr/lib/locale/en_US.utf8/LC_CTYPE 2aaaaab0e000-2aaaaab15000 r--s > 00000000 08:06 297966 /usr/lib64/gconv/gconv-modules.cache > 2aaaaab15000-2aaaaab17000 r--s 00000000 08:06 493515 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/dnsns.jar > 2aaaaab17000-2aaaaabdb000 r--s 00000000 08:06 493516 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/localedata.jar > 2aaaaabdb000-2aaaaac02000 r--s 00000000 08:06 493517 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/ > sunjce_provider.jar > 2aaaaac02000-2aaaaac08000 r--s 00000000 08:06 698398 > /root/aidajni-3.2.6/lib/freehep-aidajni-3.2.6.jar > 2aaaaac08000-2aaaaac14000 r--s 00000000 08:06 730411 > /root/jaida-3.3.0-2/lib/optimizers-20020927.jar > 2aaaaac14000-2aaaaac24000 r--s 00000000 08:06 730417 > /root/jaida-3.3.0-2/lib/openide-lookup-1.9-patched-1.0.jar > 2aaaaac24000-2aaaaac93000 r--s 00000000 08:06 730414 > /root/jaida-3.3.0-2/lib/l2fprod-common-all-6.9.1.jar > 2aaaaac93000-2aaaaacb1000 r--s 00000000 08:06 730403 > /root/jaida-3.3.0-2/lib/junit-3.8.2.jar 2aaaaacb1000-2aaaaacba000 r--s > 00000000 08:06 730395 /root/jaida-3.3.0-2/lib/jel-0.9.10.jar > 2aaaaacba000-2aaaaace0000 r--s 00000000 08:06 730404 > /root/jaida-3.3.0-2/lib/jdom-1.0.jar 2aaaaace0000-2aaaaad91000 r--s > 00000000 08:06 730392 /root/jaida-3.3.0-2/lib/jas-plotter-2.1.jar > 2aaaaad91000-2aaaaadb7000 r--s 00000000 08:06 730412 > /root/jaida-3.3.0-2/lib/freehep-xml-2.0.1.jar > 2aaaaadb7000-2aaaaadc4000 > r--s 00000000 08:06 730393 > /root/jaida-3.3.0-2/lib/freehep-util-2.0.1.jar > 2aaaaadc4000-2aaaaadf9000 > r--s 00000000 08:06 730428 > /root/jaida-3.3.0-2/lib/freehep-swing-2.0.2.jar > 2aaaaadf9000-2aaaaae3c000 r--s 00000000 08:06 730402 > /root/jaida-3.3.0-2/lib/freehep-rootio-2.0.jar > 2aaaaae3c000-2aaaaaeba000 > r--s 00000000 08:06 730425 /root/jaida-3.3.0-2/lib/bcel-5.1.jar > 2aaaaaeba000-2aaaaaed9000 r--s 00000000 08:06 730423 > /root/jaida-3.3.0-2/lib/freehep-jminuit-jdk1.4-1.0.jar > 2aaaaaed9000-2aaaaaee1000 r--s 00000000 08:06 730408 > /root/jaida-3.3.0-2/lib/freehep-jaida-root-3.3.0-2.jar > 2aaaaaee1000-2aaaaaf27000 r--s 00000000 08:06 730429 > /root/jaida-3.3.0-2/lib/freehep-jaida-remote-3.3.0-2.jar > 2aaaaaf27000-2aaaaaf2a000 r--s 00000000 08:06 730401 > /root/jaida-3.3.0-2/lib/freehep-jaida-jminuit-3.3.0-2.jar > 2aaaaaf2a000-2aaaaaf2e000 r--s 00000000 08:06 730415 > /root/jaida-3.3.0-2/lib/freehep-jaida-hbook-3.3.0-2.jar > 2aaaaaf2e000-2aaaaaf32000 r--s 00000000 08:06 730421 > /root/jaida-3.3.0-2/lib/freehep-jaida-fminuit-3.3.0-2.jar > 2aaaaaf32000-2aaaab002000 r--s 00000000 08:06 730424 > /root/jaida-3.3.0-2/lib/freehep-jaida-3.3.0-2.jar > 2aaaab002000-2aaaab012000 r--s 00000000 08:06 730427 > /root/jaida-3.3.0-2/lib/freehep-io-2.0.1.jar 2aaaab012000-2aaaab01a000 > r--s 00000000 08:06 730394 /root/jaida-3.3.0-2/lib/freehep- > hbook-2.0.jar > 2aaaab01a000-2aaaab047000 r--s 00000000 08:06 730398 > /root/jaida-3.3.0-2/lib/freehep-graphicsio-swf-2.0.jar > 2aaaab047000-2aaaab04d000 r--s 00000000 08:06 730410 > /root/jaida-3.3.0-2/lib/freehep-graphicsio-svg-2.0.jar > 2aaaab04d000-2aaaab059000 r--s 00000000 08:06 730420 > /root/jaida-3.3.0-2/lib/freehep-graphicsio-ps-2.0.jar > 2aaaab059000-2aaaab06c000 r--s 00000000 08:06 730399 > /root/jaida-3.3.0-2/lib/freehep-graphicsio-pdf-2.0.jar > 2aaaab06c000-2aaaab08f000 r--s 00000000 08:06 730422 > /root/jaida-3.3.0-2/lib/freehep-graphicsio-emf-2.0.jar > 2aaaab08f000-2aaaab0bd000 r--s 00000000 08:06 730409 > /root/jaida-3.3.0-2/lib/freehep-graphicsio-2.0.jar > 2aaaab0bd000-2aaaab0db000 r--s 00000000 08:06 730400 > /root/jaida-3.3.0-2/lib/freehep-graphics2d-2.0.jar > 2aaaab0db000-2aaaab0dd000 r--s 00000000 08:06 730406 > /root/jaida-3.3.0-2/lib/freehep-fminuit-2.0.jar > 2aaaab0dd000-2aaaab0e2000 r--s 00000000 08:06 730396 > /root/jaida-3.3.0-2/lib/freehep-export-2.0.3.jar > 2aaaab0e2000-2aaaab113000 r--s 00000000 08:06 730416 > /root/jaida-3.3.0-2/lib/freehep-application-2.0.jar > 2aaaab113000-2aaaab114000 r--s 00000000 08:06 730426 > /root/jaida-3.3.0-2/lib/fortran-1.0.jar 2aaaab114000-2aaaab13f000 r--s > 00000000 08:06 730407 /root/jaida-3.3.0-2/lib/commons-math-1.1.jar > 2aaaab13f000-2aaaab147000 r--s 00000000 08:06 730413 > /root/jaida-3.3.0-2/lib/commons-logging-1.0.3.jar > 2aaaab147000-2aaaab159000 r--s 00000000 08:06 730397 > /root/jaida-3.3.0-2/lib/commons-discovery-0.2.jar > 2aaaab159000-2aaaab15a000 r--s 00000000 08:06 730419 > /root/jaida-3.3.0-2/lib/cernlib-2003-1.0.1.jar > 2aaaab15a000-2aaaab15b000 > r--s 00000000 08:06 730418 /root/jaida-3.3.0-2/lib/aida-dev-3.3.jar > 2aaaab15b000-2aaaab166000 r--s 00000000 08:06 730405 > /root/jaida-3.3.0-2/lib/aida-3.3.jar 2aaaab166000-2aaaab1d3000 r-xp > 00000000 08:06 493465 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so > 2aaaab1d3000-2aaaab2d6000 ---p 0006d000 08:06 493465 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so > 2aaaab2d6000-2aaaab2ea000 rw-p 00070000 08:06 493465 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so > 2aaaab2ea000-2aaaab30e000 rw-p 2aaaab2ea000 00:00 0 > 2aaaab30e000-2aaaab3b8000 r-xp 00000000 08:06 493482 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > libmlib_image.so > 2aaaab3b8000-2aaaab4b7000 ---p 000aa000 08:06 493482 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > libmlib_image.so > 2aaaab4b7000-2aaaab4bc000 rw-p 000a9000 08:06 493482 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > libmlib_image.so > 2aaaab4bc000-2aaaab4ee000 r-xp 00000000 08:06 493500 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/ > libmawt.so > 2aaaab4ee000-2aaaab5f0000 ---p 00032000 08:06 493500 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/ > libmawt.so > 2aaaab5f0000-2aaaab5fb000 rw-p 00034000 08:06 493500 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/ > libmawt.so > 2aaaab5fb000-2aaaab5fc000 rw-p 2aaaab5fb000 00:00 0 > 2aaaab5fc000-2aaaab678000 r-xp 00000000 08:06 493469 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > libfontmanager.so > 2aaaab678000-2aaaab778000 ---p 0007c000 08:06 493469 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > libfontmanager.so > 2aaaab778000-2aaaab78e000 rw-p 0007c000 08:06 493469 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > libfontmanager.so > 2aaaab78e000-2aaaab79f000 rw-p 2aaaab78e000 00:00 0 > 2aaaab79f000-2aaaab7a0000 r--s 00000000 08:06 1083777 > /var/cache/fontconfig/cf6c88e680607f2ab796171745f068a4-x86-64.cache-2 > 2aaaab7a0000-2aaaab7a3000 r--s 00000000 08:06 1083775 > /var/cache/fontconfig/d458be102e54cf534d1eef0dcbb02d07-x86-64.cache-2 > 2aaaab7a3000-2aaaab7aa000 r--s 00000000 08:06 1083768 > /var/cache/fontconfig/d62e99ef547d1d24cdb1bd22ec1a2976-x86-64.cache-2 > 2aaaab7aa000-2aaaab7bc000 r-xp 00000000 08:06 493484 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so > 2aaaab7bc000-2aaaab8be000 ---p 00012000 08:06 493484 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so > 2aaaab8be000-2aaaab8c1000 rw-p 00014000 08:06 493484 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so > 2aaaabe9b000-2aaaabecb000 r--s 00000000 08:06 1083773 > /var/cache/fontconfig/8d4af663993b81a124ee82e610bb31f9-x86-64.cache-2 > 2aaaabecb000-2aaaabf30000 r--s 00000000 08:06 1083765 > /var/cache/fontconfig/df311e82a1a24c41a75c2c930223552e-x86-64.cache-2 > 2aaaabf30000-2aaaabf95000 r--s 00000000 08:06 1083766 > /var/cache/fontconfig/17090aa38d5c6f09fb8c5c354938f1d7-x86-64.cache-2 > 2aaaac000000-2aaaac2ce000 rw-p 2aaaac000000 00:00 0 > 2aaaac2ce000-2aaab0000000 ---p 2aaaac2ce000 00:00 0 > 2aaab0224000-2aaab0294000 r--s 00000000 08:06 1083774 > /var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-x86-64.cache-2 > 2aaab0294000-2aaab0295000 r--s 00000000 08:06 1083780 > /var/cache/fontconfig/b6bbb9f898b73777cfe763014a8c08d3-x86-64.cache-2 > 2aaab0295000-2aaab0298000 r--s 00000000 08:06 1083781 > /var/cache/fontconfig/6307940f96b0234967c0dcf48f992dfa-x86-64.cache-2 > 2aaab0298000-2aaab029e000 r--s 00000000 08:06 1083782 > /var/cache/fontconfig/e7a9aeb6c664d7354b888275e57aa4d9-x86-64.cache-2 > 2aaab029e000-2aaab02a8000 r--s 00000000 08:06 1083769 > /var/cache/fontconfig/77e41c5059666d75f92e318d4be8c21e-x86-64.cache-2 > 2b6abb03a000-2b6abb056000 r-xp 00000000 08:06 851970 /lib64/ld-2.5.so > 2b6abb056000-2b6abb058000 rw-p 2b6abb056000 00:00 0 > 2b6abb058000-2b6abb059000 r--p 2b6abb058000 00:00 0 > 2b6abb059000-2b6abb05a000 rwxp 2b6abb059000 00:00 0 > 2b6abb08f000-2b6abb090000 rw-p 2b6abb08f000 00:00 0 > 2b6abb090000-2b6abb099000 r-xp 00000000 08:06 493494 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > native_threads/libhpi.so > 2b6abb099000-2b6abb198000 ---p 00009000 08:06 493494 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > native_threads/libhpi.so > 2b6abb198000-2b6abb19c000 rw-p 00008000 08:06 493494 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/ > native_threads/libhpi.so > 2b6abb19c000-2b6abb1d1000 r--s 00000000 08:06 1084039 > /var/run/nscd/passwd 2b6abb1d1000-2b6abb1d9000 rw-s 00000000 08:06 > 51208 > /tmp/hsperfdata_root/10943 2b6abb256000-2b6abb258000 rw-p 0001c000 > 08:06 > 851970 /lib64/ld-2.5.so 2b6abb258000-2b6abb26f000 r-xp 00000000 08:06 > 508048 /usr/lib64/libXmu.so.6.2.0 2b6abb26f000-2b6abb46f000 ---p > 00017000 08:06 508048 /usr/lib64/libXmu.so.6.2.0 > 2b6abb46f000-2b6abb471000 rw-p 00017000 08:06 508048 > /usr/lib64/libXmu.so.6.2.0 2b6abb471000-2b6abb4cc000 r-xp 00000000 > 08:06 > 507918 /usr/lib64/libXt.so.6.0.0 2b6abb4cc000-2b6abb6cc000 ---p > 0005b000 > 08:06 507918 /usr/lib64/libXt.so.6.0.0 2b6abb6cc000-2b6abb6d2000 rw-p > 0005b000 08:06 507918 /usr/lib64/libXt.so.6.0.0 > 2b6abb6d2000-2b6abb6d3000 rw-p 2b6abb6d2000 00:00 0 > 2b6abb6d3000-2b6abb6e3000 r-xp 00000000 08:06 507912 > /usr/lib64/libXext.so.6.4.0 2b6abb6e3000-2b6abb8e2000 ---p 00010000 > 08:06 507912 /usr/lib64/libXext.so.6.4.0 2b6abb8e2000-2b6abb8e4000 > rw-p > 0000f000 08:06 507912 /usr/lib64/libXext.so.6.4.0 > 2b6abb8e4000-2b6abb8e5000 rw-p 2b6abb8e4000 00:00 0 > 2b6abb8e5000-2b6abba17000 r-xp 00000000 08:06 218719 > /usr/lib64/libX11.so.6.2.0 2b6abba17000-2b6abbc17000 ---p 00132000 > 08:06 > 218719 /usr/lib64/libX11.so.6.2.0 2b6abbc17000-2b6abbc18000 r--p > 00132000 08:06 218719 /usr/lib64/libX11.so.6.2.0 > 2b6abbc18000-2b6abbc1f000 rw-p 00133000 08:06 218719 > /usr/lib64/libX11.so.6.2.0 2b6abbc1f000-2b6abbc28000 r-xp 00000000 > 08:06 > 217931 /usr/lib64/libSM.so.6.0.0 2b6abbc28000-2b6abbe28000 ---p > 00009000 > 08:06 217931 /usr/lib64/libSM.so.6.0.0 2b6abbe28000-2b6abbe2a000 rw-p > 00009000 08:06 217931 /usr/lib64/libSM.so.6.0.0 > 2b6abbe2a000-2b6abbe41000 r-xp 00000000 08:06 216934 > /usr/lib64/libICE.so.6.3.0 2b6abbe41000-2b6abc040000 ---p 00017000 > 08:06 > 216934 /usr/lib64/libICE.so.6.3.0 2b6abc040000-2b6abc042000 rw-p > 00016000 08:06 216934 /usr/lib64/libICE.so.6.3.0 > 2b6abc042000-2b6abc047000 rw-p 2b6abc042000 00:00 0 > 2b6abc047000-2b6abc193000 r-xp 00000000 08:06 985493 > /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc193000-2b6abc393000 ---p > 0014c000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so > 2b6abc393000-2b6abc399000 r--p 0014c000 08:06 985493 > /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc399000-2b6abc39b000 rw-p > 00152000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so > 2b6abc39b000-2b6abc39e000 rw-p 2b6abc39b000 00:00 0 > 2b6abc39e000-2b6abca69000 r-xp 00000000 08:06 493498 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/ > libjvm.so > 2b6abca69000-2b6abcb68000 ---p 006cb000 08:06 493498 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/ > libjvm.so > 2b6abcb68000-2b6abcce3000 rw-p 006ca000 08:06 493498 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/ > libjvm.so > 2b6abcce3000-2b6abcd12000 rw-p 2b6abcce3000 00:00 0 > 2b6abcd12000-2b6abcdf5000 r-xp 00000000 08:06 217112 > /usr/lib64/libstdc++.so.6.0.8 2b6abcdf5000-2b6abcff5000 ---p 000e3000 > 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcff5000-2b6abcffb000 > r--p 000e3000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 > 2b6abcffb000-2b6abcffe000 rw-p 000e9000 08:06 217112 > /usr/lib64/libstdc++.so.6.0.8 2b6abcffe000-2b6abd011000 rw-p > 2b6abcffe000 00:00 0 2b6abd011000-2b6abd066000 r-xp 00000000 08:06 > 851985 /lib64/libm-2.5.so 2b6abd066000-2b6abd265000 ---p 00055000 > 08:06 > 851985 /lib64/libm-2.5.so 2b6abd265000-2b6abd267000 rw-p 00054000 > 08:06 > 851985 /lib64/libm-2.5.so 2b6abd267000-2b6abd274000 r-xp 00000000 > 08:06 > 852021 /lib64/libgcc_s.so.1 2b6abd274000-2b6abd473000 ---p 0000d000 > 08:06 852021 /lib64/libgcc_s.so.1 2b6abd473000-2b6abd475000 rw-p > 0000c000 08:06 852021 /lib64/libgcc_s.so.1 2b6abd475000-2b6abd5ae000 > r-xp 00000000 08:06 851977 /lib64/libc-2.5.so > 2b6abd5ae000-2b6abd7ad000 > ---p 00139000 08:06 851977 /lib64/libc-2.5.so > 2b6abd7ad000-2b6abd7b0000 > r--p 00138000 08:06 851977 /lib64/libc-2.5.so > 2b6abd7b0000-2b6abd7b2000 > rw-p 0013b000 08:06 851977 /lib64/libc-2.5.so > 2b6abd7b2000-2b6abd7b8000 > rw-p 2b6abd7b2000 00:00 0 2b6abd7b8000-2b6abd7bd000 r-xp 00000000 > 08:06 > 216938 /usr/lib64/libXdmcp.so.6.0.0 2b6abd7bd000-2b6abd9bc000 ---p > 00005000 08:06 216938 /usr/lib64/libXdmcp.so.6.0.0 > 2b6abd9bc000-2b6abd9be000 rw-p 00004000 08:06 216938 > /usr/lib64/libXdmcp.so.6.0.0 2b6abd9be000-2b6abd9d4000 r-xp 00000000 > 08:06 852003 /lib64/libpthread-2.5.so 2b6abd9d4000-2b6abdbd3000 ---p > 00016000 08:06 852003 /lib64/libpthread-2.5.so > 2b6abdbd3000-2b6abdbd5000 > rw-p 00015000 08:06 852003 /lib64/libpthread-2.5.so > 2b6abdbd5000-2b6abdbd9000 rw-p 2b6abdbd5000 00:00 0 > 2b6abdbd9000-2b6abdbdb000 r-xp 00000000 08:06 216936 > /usr/lib64/libXau.so.6.0.0 2b6abdbdb000-2b6abddda000 ---p 00002000 > 08:06 > 216936 /usr/lib64/libXau.so.6.0.0 2b6abddda000-2b6abdddc000 rw-p > 00001000 08:06 216936 /usr/lib64/libXau.so.6.0.0 > 2b6abdddc000-2b6abdddd000 rw-p 2b6abdddc000 00:00 0 > 2b6abdddd000-2b6abdddf000 r-xp 00000000 08:06 851983 /lib64/ > libdl-2.5.so > 2b6abdddf000-2b6abdfdf000 ---p 00002000 08:06 851983 /lib64/ > libdl-2.5.so > 2b6abdfdf000-2b6abdfe1000 rw-p 00002000 08:06 851983 /lib64/ > libdl-2.5.so > 2b6abdfe1000-2b6abdfe3000 rw-p 2b6abdfe1000 00:00 0 > 2b6abdfe3000-2b6abdff7000 r-xp 00000000 08:06 851988 > /lib64/libnsl-2.5.so 2b6abdff7000-2b6abe1f6000 ---p 00014000 08:06 > 851988 /lib64/libnsl-2.5.so 2b6abe1f6000-2b6abe1f8000 rw-p 00013000 > 08:06 851988 /lib64/libnsl-2.5.so 2b6abe1f8000-2b6abe1fa000 rw-p > 2b6abe1f8000 00:00 0 2b6abe1fa000-2b6abe207000 r-xp 00000000 08:06 > 493489 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so > 2b6abe207000-2b6abe306000 ---p 0000d000 08:06 493489 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so > 2b6abe306000-2b6abe309000 rw-p 0000c000 08:06 493489 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so > 2b6abe309000-2b6abe32e000 r-xp 00000000 08:06 493474 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so > 2b6abe32e000-2b6abe42d000 ---p 00025000 08:06 493474 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so > 2b6abe42d000-2b6abe433000 rw-p 00024000 08:06 493474 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so > 2b6abe433000-2b6abe442000 r-xp 00000000 08:06 493490 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so > 2b6abe442000-2b6abe543000 ---p 0000f000 08:06 493490 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so > 2b6abe543000-2b6abe547000 rw-p 00010000 08:06 493490 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so > 2b6abe547000-2b6ac0b5d000 r--s 00000000 08:06 493583 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/rt.jar > 2b6ac0b5d000-2b6ac0bc6000 rw-p 2b6ac0b5d000 00:00 0 > 2b6ac0bc6000-2b6ac0c4b000 r--s 00000000 08:06 493566 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/jsse.jar > 2b6ac0c4b000-2b6ac0c60000 r--s 00000000 08:06 493565 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/jce.jar > 2b6ac0c60000-2b6ac14d0000 r--s 00000000 08:06 493504 > /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/charsets.jar > 2b6ac14d0000-2b6ac1740000 rwxp 2b6ac14d0000 00:00 0 > 2b6ac1740000-2b6ac44d0000 rwxp 2b6ac1740000 00:00 0 > 2b6ac44d0000-2b6ac44da000 rwxp 2b6ac44d0000 00:00 0 > 2b6ac44da000-2b6ac4590000 rwxp 2b6ac44da000 00:00 0 > 2b6ac4590000-2b6ac5a50000 rwxp 2b6ac4590000 00:00 0 > 2b6ac5a50000-2b6ac9790000 rwxp 2b6ac5a50000 00:00 0 > 2b6ac9790000-2b6acac90000 rwxp 2b6ac9790000 00:00 0 > 2b6acac90000-2b6ade790000 rwxp 2b6acac90000 00:00 0 > 2b6ade790000-2b6adf9f0000 rwxp 2b6ade790000 00:00 0 > 2b6adf9f0000-2b6ae8f90000 rwxp 2b6adf9f0000 00:00 0 > 2b6ae8f90000-2b6ae8f9b000 rwxp 2b6ae8f90000 00:00 0 > 2b6ae8f9b000-2b6ae8fb9000 rwxp 2b6ae8f9b000 00:00 0 > 2b6ae8fb9000-2b6ae8fc4000 rwxp 2b6ae8fb9000 00:00 0 > 2b6ae8fc4000-2b6ae9061000 rwxp 2b6ae8fc4000 00:00 0 > 2b6ae9061000-2b6ae906b000 rwxp 2b6ae9061000 00:00 0 > 2b6ae906b000-2b6ae90b5000 rwxp 2b6ae906b000 00:00 0 > 2b6ae90b5000-2b6ae90c1000 rwxp 2b6ae90b5000 00:00 0 > 2b6ae90c1000-2b6ae915e000 rwxp 2b6ae90c1000 00:00 0 > 2b6ae915e000-2b6ae9169000 rwxp 2b6ae915e000 00:00 0 > 2b6ae9169000-2b6ae9187000 rwxp 2b6ae9169000 00:00 0 > 7fffef86d000-7fffef870000 ---p 7fffef86d000 00:00 0 > 7fffef870000-7fffefa6d000 rwxp 7fffef870000 00:00 0 [stack] > 7fffefa6d000-7fffefa70000 rw-p 7fffefa6d000 00:00 0 > ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso] > > VM Arguments: > > java_command: <unknown> > > Launcher Type: generic > > Environment Variables: JAVA_HOME=/usr/lib64/jvm/java > JRE_HOME=/usr/lib64/jvm/java/jre > PATH=/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/aidajni-3.2.6/ > bin/amd64-Linux-g++:/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/ > aidajni-3.2.6/bin/amd64-Linux-g++:/sbin:/usr/sbin:/usr/local/sbin:/ > opt/kde3/sbin:/opt/gnome/sbin:/root/bin:/usr/local/bin:/usr/bin:/ > usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/ > mit/bin:/usr/lib/mit/sbin:/usr/lib/qt3/bin:/home/G4Workdir/bin/ > Linux-g++:/home/G4Workdir/bin/Linux-g++:/home/G4Workdir/bin/Linux-g++ > LD_LIBRARY_PATH=/usr/lib64/jvm/java/jre/lib/amd64:/usr/lib64/jvm/ > java/jre/lib/amd64/server:/root/aidajni-3.2.6/lib/amd64-Linux-g++:/ > root/2.0.3.1/CLHEP > SHELL=/bin/bash DISPLAY=:0.0 HOSTTYPE=x86_64 OSTYPE=linux > MACHTYPE=x86_64-suse-linux > > Signal Handlers: > > SIGSEGV: [libjvm.so+0x656380], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGBUS: [libjvm.so+0x656380], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGFPE: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGPIPE: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGILL: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGUSR1: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000 > SIGUSR2: [libjvm.so+0x55fc00], sa_mask[0]=0x00000000, > sa_flags=0x14000004 > SIGHUP: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGINT: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGQUIT: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > SIGTERM: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, > sa_flags=0x14000004 > > --------------- S Y S T E M --------------- > > OS:openSUSE 10.2 (X86-64) VERSION = 10.2 > > uname:Linux 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 > x86_64 libc:glibc 2.5 NPTL 2.5 > > rlimit: STACK 8192k, CORE 0k, NPROC 16382, NOFILE 8192, AS 2882320k > > load average:0.41 0.27 0.20 > > CPU:total 2 em64t ht > > Memory: 4k page, physical 2060636k(907992k free), swap 1542200k > (1542200k free) > > vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03) for linux- > amd64, built on Jun 28 2006 00:27:03 by java_re with gcc 3.2.2 > (SuSE Linux) >

Re: Aida and exA01 on x86_64 by Theo <Theo>, 07 May, 2007 Re: Re: Aida and exA01 on x86_64 (Mark Donszelmann) i don't know if that helps but i copy paste the full log report.it's a little bit big.Well here it is: # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x00002b6abb0431b6, pid=10943, tid=47737454076704 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03 mixed mode) # Problematic frame: # C [ld-linux-x86-64.so.2+0x91b6] # --------------- T H R E A D --------------- Current thread (0x00000000011f2d90): JavaThread "main" [_thread_in_native, id=10943] siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x0000000000000000 Registers: RAX=0x0000000000000000, RBX=0x00002b6abb257628, RCX=0x0377cc14b1b73c55, RDX=0x00000000b1b73c55 RSP=0x00007fffefa69b90, RBP=0x00007fffefa69ca0, RSI=0x00002b6abb257628, RDI=0x00002aaaab7bb6be R8 =0x0000000000000000, R9 =0x0000000000000000, R10=0x0000000000000000, R11=0x00000000ffffffff R12=0x0000000000000000, R13=0x00000000b1b73c55, R14=0x00002aaaab7bb6b5, R15=0x0000000000000000 RIP=0x00002b6abb0431b6, EFL=0x0000000000010246, CSGSFS=0x0000000000000033, ERR=0x0000000000000004 TRAPNO=0x000000000000000e Top of Stack: (sp=0x00007fffefa69b90) 0x00007fffefa69b90: 00007fffefa69b90 00002b6ac460d4e0 0x00007fffefa69ba0: 00007fffefa69bd8 00002b6ac469a290 0x00007fffefa69bb0: 0000000000000000 00002b6ac460d4f8 0x00007fffefa69bc0: 00007fffefa69bd8 00007fffefa69c18 0x00007fffefa69bd0: 00002b6ac14d2d36 0000000000000000 0x00007fffefa69be0: 00007fffefa69be0 00000000c460d336 0x00007fffefa69bf0: 0000000000000000 00007fffefa69d00 0x00007fffefa69c00: 00002b6abb257628 00002b6ac460d358 0x00007fffefa69c10: 00007fffefa69c38 00007fffefa69ca0 0x00007fffefa69c20: 00002b6ac14d032d 0000000000000000 0x00007fffefa69c30: 0000000000000000 00002b6ade877060 0x00007fffefa69c40: 0000000000001fa0 00002b6abd476b44 0x00007fffefa69c50: 0000000000000000 0000000000000000 0x00007fffefa69c60: 00002b6abc3a2fbe 00000000ffffffff 0x00007fffefa69c70: 00007fffefa69d10 00002b6abb257628 0x00007fffefa69c80: 0000000000000000 00002b6abb256be0 0x00007fffefa69c90: 00002b6abcbeb1a0 00002aaaac221d60 0x00007fffefa69ca0: 00002aaaab7bb6b5 00002b6abd567d95 0x00007fffefa69cb0: 0000000000000003 0000000000000000 0x00007fffefa69cc0: 00007fffefa69e28 00002b6abd478ac8 0x00007fffefa69cd0: 0000000000000000 00002b6abdddce40 0x00007fffefa69ce0: 00002b6abd0109b0 00002b6abc3a26a4 0x00007fffefa69cf0: 00002b6abd484d80 00002b6abc39f438 0x00007fffefa69d00: 0000000000000000 000000010000003c 0x00007fffefa69d10: 00000000011f2d90 00007fffefa69eb0 0x00007fffefa69d20: 00007fffefa69eb0 00002b6abddde240 0x00007fffefa69d30: 0000000000000007 00002b6abcbeb1a0 0x00007fffefa69d40: 00002aaaac221d60 00002b6abddde254 0x00007fffefa69d50: 0000000000000000 00002b6abb0470c6 0x00007fffefa69d60: 00007fffefa69eb0 00002b6abddde240 0x00007fffefa69d70: 00000000011ef608 00000000011ef618 0x00007fffefa69d80: 00000000011ef610 00002b6abdfe2300 Instructions: (pc=0x00002b6abb0431b6) 0x00002b6abb0431a6: 0f 85 79 03 00 00 48 8b 85 50 ff ff ff 45 31 d2 0x00002b6abb0431b6: 48 8b 10 31 c0 48 85 d2 0f 84 59 03 00 00 48 8b Stack: [0x00007fffef86d000,0x00007fffefa6d000), sp=0x00007fffefa69b90, free space=2034k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [ld-linux-x86-64.so.2+0x91b6] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/String;)V+0 j java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/File;)Z+300 j java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/String;Z)V+217 j java.lang.Runtime.loadLibrary0(Ljava/lang/Class;Ljava/lang/String;)V+54 j java.lang.System.loadLibrary(Ljava/lang/String;)V+7 j sun.security.action.LoadLibraryAction.run()Ljava/lang/Object;+4 v ~StubRoutines::call_stub j java.security.AccessController.doPrivileged(Ljava/security/PrivilegedAction;)Ljava/lang/Object;+0 j sun.nio.ch.Util.load()V+28 j sun.nio.ch.FileChannelImpl.<clinit>()V+29 v ~StubRoutines::call_stub j java.io.RandomAccessFile.getChannel()Ljava/nio/channels/FileChannel;+22 j sun.font.TrueTypeFont.open()Ljava/nio/channels/FileChannel;+30 j sun.font.TrueTypeFont.verify()V+1 j sun.font.TrueTypeFont.<init>(Ljava/lang/String;Ljava/lang/Object;IZ)V+40 j sun.font.FontManager.registerFontFile(Ljava/lang/String;[Ljava/lang/String;IZI)Lsun/font/PhysicalFont;+55 j sun.font.FontManager.initialiseDeferredFont(Ljava/lang/String;)Lsun/font/PhysicalFont;+80 j sun.font.FontManager.initialiseDeferredFonts()V+32 j sun.java2d.SunGraphicsEnvironment.loadFonts()V+30 j sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames(Ljava/util/Locale;)[Ljava/lang/String;+60 j sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames()[Ljava/lang/String;+4 j hep.aida.ref.plotter.FontStyleParameter.<clinit>()V+3 v ~StubRoutines::call_stub j hep.aida.ref.plotter.TextStyle.initializeBaseStyle()V+5 j hep.aida.ref.plotter.BaseStyle.<init>()V+60 j hep.aida.ref.plotter.BrushStyle.<init>()V+1 j hep.aida.ref.plotter.TextStyle.<init>()V+1 j hep.aida.ref.plotter.InfoStyle.initializeBaseStyle()V+5 j hep.aida.ref.plotter.BaseStyle.<init>()V+60 j hep.aida.ref.plotter.InfoStyle.<init>()V+1 j hep.aida.ref.plotter.PlotterStyle.initializeBaseStyle()V+45 j hep.aida.ref.plotter.BaseStyle.<init>()V+60 j hep.aida.ref.plotter.PlotterStyle.<init>()V+1 j hep.aida.ref.plotter.DummyPlotter.<init>(Ljava/lang/String;Ljava/lang/String;)V+53 j hep.aida.ref.plotter.Plotter.<init>(Ljava/lang/String;Ljava/lang/String;)V+3 j hep.aida.ref.plotter.PlotterFactory.create(Ljava/lang/String;Ljava/lang/String;)Lhep/aida/IPlotter;+6 j hep.aida.ref.plotter.PlotterFactory.create(Ljava/lang/String;)Lhep/aida/IPlotter;+3 v ~StubRoutines::call_stub --------------- P R O C E S S --------------- Java Threads: ( => current thread ) 0x00002aaaac245470 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=10955] 0x00000000012db990 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=10953] 0x00000000012d9d60 JavaThread "CompilerThread1" daemon [_thread_in_native, id=10952] 0x00000000012d87b0 JavaThread "CompilerThread0" daemon [_thread_in_native, id=10951] 0x00000000012d7050 JavaThread "AdapterThread" daemon [_thread_in_vm, id=10950] 0x00000000012d5d10 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=10949] 0x00000000012c1310 JavaThread "Finalizer" daemon [_thread_blocked, id=10948] 0x00000000012c0ae0 JavaThread "Reference Handler" daemon [_thread_blocked, id=10947] =>0x00000000011f2d90 JavaThread "main" [_thread_in_native, id=10943] Other Threads: 0x00000000012bc5d0 VMThread [id=10946] 0x00000000012dd5e0 WatcherThread [id=10954] VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None Heap PSYoungGen total 9408K, used 2320K [0x00002b6ade790000, 0x00002b6adf9f0000, 0x00002b6ae8f90000) eden space 8064K, 12% used [0x00002b6ade790000,0x00002b6ade8882d8,0x00002b6adef70000) from space 1344K, 98% used [0x00002b6adef70000,0x00002b6adf0bc030,0x00002b6adf0c0000) to space 1344K, 0% used [0x00002b6adf8a0000,0x00002b6adf8a0000,0x00002b6adf9f0000) PSOldGen total 21504K, used 728K [0x00002b6ac9790000, 0x00002b6acac90000, 0x00002b6ade790000) object space 21504K, 3% used [0x00002b6ac9790000,0x00002b6ac9846018,0x00002b6acac90000) PSPermGen total 21248K, used 5599K [0x00002b6ac4590000, 0x00002b6ac5a50000, 0x00002b6ac9790000) object space 21248K, 26% used [0x00002b6ac4590000,0x00002b6ac4b07d18,0x00002b6ac5a50000) Dynamic libraries: 00400000-00ae9000 r-xp 00000000 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app 00ce9000-00ceb000 r--p 006e9000 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app 00ceb000-00d26000 rw-p 006eb000 08:07 1458305 /home/G4Workdir/bin/Linux-g++/A01app 00d26000-018cd000 rw-p 00d26000 00:00 0 [heap] 40000000-40001000 ---p 40000000 00:00 0 40001000-40101000 rwxp 40001000 00:00 0 40101000-40102000 ---p 40101000 00:00 0 40102000-40202000 rwxp 40102000 00:00 0 40202000-40203000 ---p 40202000 00:00 0 40203000-40303000 rwxp 40203000 00:00 0 40303000-40306000 ---p 40303000 00:00 0 40306000-40404000 rwxp 40306000 00:00 0 40404000-40407000 ---p 40404000 00:00 0 40407000-40505000 rwxp 40407000 00:00 0 40505000-40508000 ---p 40505000 00:00 0 40508000-40606000 rwxp 40508000 00:00 0 40606000-40609000 ---p 40606000 00:00 0 40609000-40707000 rwxp 40609000 00:00 0 40707000-4070a000 ---p 40707000 00:00 0 4070a000-40808000 rwxp 4070a000 00:00 0 40808000-4080b000 ---p 40808000 00:00 0 4080b000-40909000 rwxp 4080b000 00:00 0 40909000-4090c000 ---p 40909000 00:00 0 4090c000-40a0a000 rwxp 4090c000 00:00 0 40a0a000-40a0b000 ---p 40a0a000 00:00 0 40a0b000-40b0b000 rwxp 40a0b000 00:00 0 40b0b000-40b0e000 ---p 40b0b000 00:00 0 40b0e000-40c0c000 rwxp 40b0e000 00:00 0 2aaaaaaab000-2aaaaaad3000 rw-p 2aaaaaaab000 00:00 0 2aaaaaad3000-2aaaaab0e000 r--p 00000000 08:06 314936 /usr/lib/locale/en_US.utf8/LC_CTYPE 2aaaaab0e000-2aaaaab15000 r--s 00000000 08:06 297966 /usr/lib64/gconv/gconv-modules.cache 2aaaaab15000-2aaaaab17000 r--s 00000000 08:06 493515 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/dnsns.jar 2aaaaab17000-2aaaaabdb000 r--s 00000000 08:06 493516 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/localedata.jar 2aaaaabdb000-2aaaaac02000 r--s 00000000 08:06 493517 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/ext/sunjce_provider.jar 2aaaaac02000-2aaaaac08000 r--s 00000000 08:06 698398 /root/aidajni-3.2.6/lib/freehep-aidajni-3.2.6.jar 2aaaaac08000-2aaaaac14000 r--s 00000000 08:06 730411 /root/jaida-3.3.0-2/lib/optimizers-20020927.jar 2aaaaac14000-2aaaaac24000 r--s 00000000 08:06 730417 /root/jaida-3.3.0-2/lib/openide-lookup-1.9-patched-1.0.jar 2aaaaac24000-2aaaaac93000 r--s 00000000 08:06 730414 /root/jaida-3.3.0-2/lib/l2fprod-common-all-6.9.1.jar 2aaaaac93000-2aaaaacb1000 r--s 00000000 08:06 730403 /root/jaida-3.3.0-2/lib/junit-3.8.2.jar 2aaaaacb1000-2aaaaacba000 r--s 00000000 08:06 730395 /root/jaida-3.3.0-2/lib/jel-0.9.10.jar 2aaaaacba000-2aaaaace0000 r--s 00000000 08:06 730404 /root/jaida-3.3.0-2/lib/jdom-1.0.jar 2aaaaace0000-2aaaaad91000 r--s 00000000 08:06 730392 /root/jaida-3.3.0-2/lib/jas-plotter-2.1.jar 2aaaaad91000-2aaaaadb7000 r--s 00000000 08:06 730412 /root/jaida-3.3.0-2/lib/freehep-xml-2.0.1.jar 2aaaaadb7000-2aaaaadc4000 r--s 00000000 08:06 730393 /root/jaida-3.3.0-2/lib/freehep-util-2.0.1.jar 2aaaaadc4000-2aaaaadf9000 r--s 00000000 08:06 730428 /root/jaida-3.3.0-2/lib/freehep-swing-2.0.2.jar 2aaaaadf9000-2aaaaae3c000 r--s 00000000 08:06 730402 /root/jaida-3.3.0-2/lib/freehep-rootio-2.0.jar 2aaaaae3c000-2aaaaaeba000 r--s 00000000 08:06 730425 /root/jaida-3.3.0-2/lib/bcel-5.1.jar 2aaaaaeba000-2aaaaaed9000 r--s 00000000 08:06 730423 /root/jaida-3.3.0-2/lib/freehep-jminuit-jdk1.4-1.0.jar 2aaaaaed9000-2aaaaaee1000 r--s 00000000 08:06 730408 /root/jaida-3.3.0-2/lib/freehep-jaida-root-3.3.0-2.jar 2aaaaaee1000-2aaaaaf27000 r--s 00000000 08:06 730429 /root/jaida-3.3.0-2/lib/freehep-jaida-remote-3.3.0-2.jar 2aaaaaf27000-2aaaaaf2a000 r--s 00000000 08:06 730401 /root/jaida-3.3.0-2/lib/freehep-jaida-jminuit-3.3.0-2.jar 2aaaaaf2a000-2aaaaaf2e000 r--s 00000000 08:06 730415 /root/jaida-3.3.0-2/lib/freehep-jaida-hbook-3.3.0-2.jar 2aaaaaf2e000-2aaaaaf32000 r--s 00000000 08:06 730421 /root/jaida-3.3.0-2/lib/freehep-jaida-fminuit-3.3.0-2.jar 2aaaaaf32000-2aaaab002000 r--s 00000000 08:06 730424 /root/jaida-3.3.0-2/lib/freehep-jaida-3.3.0-2.jar 2aaaab002000-2aaaab012000 r--s 00000000 08:06 730427 /root/jaida-3.3.0-2/lib/freehep-io-2.0.1.jar 2aaaab012000-2aaaab01a000 r--s 00000000 08:06 730394 /root/jaida-3.3.0-2/lib/freehep-hbook-2.0.jar 2aaaab01a000-2aaaab047000 r--s 00000000 08:06 730398 /root/jaida-3.3.0-2/lib/freehep-graphicsio-swf-2.0.jar 2aaaab047000-2aaaab04d000 r--s 00000000 08:06 730410 /root/jaida-3.3.0-2/lib/freehep-graphicsio-svg-2.0.jar 2aaaab04d000-2aaaab059000 r--s 00000000 08:06 730420 /root/jaida-3.3.0-2/lib/freehep-graphicsio-ps-2.0.jar 2aaaab059000-2aaaab06c000 r--s 00000000 08:06 730399 /root/jaida-3.3.0-2/lib/freehep-graphicsio-pdf-2.0.jar 2aaaab06c000-2aaaab08f000 r--s 00000000 08:06 730422 /root/jaida-3.3.0-2/lib/freehep-graphicsio-emf-2.0.jar 2aaaab08f000-2aaaab0bd000 r--s 00000000 08:06 730409 /root/jaida-3.3.0-2/lib/freehep-graphicsio-2.0.jar 2aaaab0bd000-2aaaab0db000 r--s 00000000 08:06 730400 /root/jaida-3.3.0-2/lib/freehep-graphics2d-2.0.jar 2aaaab0db000-2aaaab0dd000 r--s 00000000 08:06 730406 /root/jaida-3.3.0-2/lib/freehep-fminuit-2.0.jar 2aaaab0dd000-2aaaab0e2000 r--s 00000000 08:06 730396 /root/jaida-3.3.0-2/lib/freehep-export-2.0.3.jar 2aaaab0e2000-2aaaab113000 r--s 00000000 08:06 730416 /root/jaida-3.3.0-2/lib/freehep-application-2.0.jar 2aaaab113000-2aaaab114000 r--s 00000000 08:06 730426 /root/jaida-3.3.0-2/lib/fortran-1.0.jar 2aaaab114000-2aaaab13f000 r--s 00000000 08:06 730407 /root/jaida-3.3.0-2/lib/commons-math-1.1.jar 2aaaab13f000-2aaaab147000 r--s 00000000 08:06 730413 /root/jaida-3.3.0-2/lib/commons-logging-1.0.3.jar 2aaaab147000-2aaaab159000 r--s 00000000 08:06 730397 /root/jaida-3.3.0-2/lib/commons-discovery-0.2.jar 2aaaab159000-2aaaab15a000 r--s 00000000 08:06 730419 /root/jaida-3.3.0-2/lib/cernlib-2003-1.0.1.jar 2aaaab15a000-2aaaab15b000 r--s 00000000 08:06 730418 /root/jaida-3.3.0-2/lib/aida-dev-3.3.jar 2aaaab15b000-2aaaab166000 r--s 00000000 08:06 730405 /root/jaida-3.3.0-2/lib/aida-3.3.jar 2aaaab166000-2aaaab1d3000 r-xp 00000000 08:06 493465 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so 2aaaab1d3000-2aaaab2d6000 ---p 0006d000 08:06 493465 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so 2aaaab2d6000-2aaaab2ea000 rw-p 00070000 08:06 493465 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libawt.so 2aaaab2ea000-2aaaab30e000 rw-p 2aaaab2ea000 00:00 0 2aaaab30e000-2aaaab3b8000 r-xp 00000000 08:06 493482 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libmlib_image.so 2aaaab3b8000-2aaaab4b7000 ---p 000aa000 08:06 493482 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libmlib_image.so 2aaaab4b7000-2aaaab4bc000 rw-p 000a9000 08:06 493482 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libmlib_image.so 2aaaab4bc000-2aaaab4ee000 r-xp 00000000 08:06 493500 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/libmawt.so 2aaaab4ee000-2aaaab5f0000 ---p 00032000 08:06 493500 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/libmawt.so 2aaaab5f0000-2aaaab5fb000 rw-p 00034000 08:06 493500 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/xawt/libmawt.so 2aaaab5fb000-2aaaab5fc000 rw-p 2aaaab5fb000 00:00 0 2aaaab5fc000-2aaaab678000 r-xp 00000000 08:06 493469 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libfontmanager.so 2aaaab678000-2aaaab778000 ---p 0007c000 08:06 493469 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libfontmanager.so 2aaaab778000-2aaaab78e000 rw-p 0007c000 08:06 493469 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libfontmanager.so 2aaaab78e000-2aaaab79f000 rw-p 2aaaab78e000 00:00 0 2aaaab79f000-2aaaab7a0000 r--s 00000000 08:06 1083777 /var/cache/fontconfig/cf6c88e680607f2ab796171745f068a4-x86-64.cache-2 2aaaab7a0000-2aaaab7a3000 r--s 00000000 08:06 1083775 /var/cache/fontconfig/d458be102e54cf534d1eef0dcbb02d07-x86-64.cache-2 2aaaab7a3000-2aaaab7aa000 r--s 00000000 08:06 1083768 /var/cache/fontconfig/d62e99ef547d1d24cdb1bd22ec1a2976-x86-64.cache-2 2aaaab7aa000-2aaaab7bc000 r-xp 00000000 08:06 493484 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so 2aaaab7bc000-2aaaab8be000 ---p 00012000 08:06 493484 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so 2aaaab8be000-2aaaab8c1000 rw-p 00014000 08:06 493484 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libnet.so 2aaaabe9b000-2aaaabecb000 r--s 00000000 08:06 1083773 /var/cache/fontconfig/8d4af663993b81a124ee82e610bb31f9-x86-64.cache-2 2aaaabecb000-2aaaabf30000 r--s 00000000 08:06 1083765 /var/cache/fontconfig/df311e82a1a24c41a75c2c930223552e-x86-64.cache-2 2aaaabf30000-2aaaabf95000 r--s 00000000 08:06 1083766 /var/cache/fontconfig/17090aa38d5c6f09fb8c5c354938f1d7-x86-64.cache-2 2aaaac000000-2aaaac2ce000 rw-p 2aaaac000000 00:00 0 2aaaac2ce000-2aaab0000000 ---p 2aaaac2ce000 00:00 0 2aaab0224000-2aaab0294000 r--s 00000000 08:06 1083774 /var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-x86-64.cache-2 2aaab0294000-2aaab0295000 r--s 00000000 08:06 1083780 /var/cache/fontconfig/b6bbb9f898b73777cfe763014a8c08d3-x86-64.cache-2 2aaab0295000-2aaab0298000 r--s 00000000 08:06 1083781 /var/cache/fontconfig/6307940f96b0234967c0dcf48f992dfa-x86-64.cache-2 2aaab0298000-2aaab029e000 r--s 00000000 08:06 1083782 /var/cache/fontconfig/e7a9aeb6c664d7354b888275e57aa4d9-x86-64.cache-2 2aaab029e000-2aaab02a8000 r--s 00000000 08:06 1083769 /var/cache/fontconfig/77e41c5059666d75f92e318d4be8c21e-x86-64.cache-2 2b6abb03a000-2b6abb056000 r-xp 00000000 08:06 851970 /lib64/ld-2.5.so 2b6abb056000-2b6abb058000 rw-p 2b6abb056000 00:00 0 2b6abb058000-2b6abb059000 r--p 2b6abb058000 00:00 0 2b6abb059000-2b6abb05a000 rwxp 2b6abb059000 00:00 0 2b6abb08f000-2b6abb090000 rw-p 2b6abb08f000 00:00 0 2b6abb090000-2b6abb099000 r-xp 00000000 08:06 493494 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/native_threads/libhpi.so 2b6abb099000-2b6abb198000 ---p 00009000 08:06 493494 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/native_threads/libhpi.so 2b6abb198000-2b6abb19c000 rw-p 00008000 08:06 493494 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/native_threads/libhpi.so 2b6abb19c000-2b6abb1d1000 r--s 00000000 08:06 1084039 /var/run/nscd/passwd 2b6abb1d1000-2b6abb1d9000 rw-s 00000000 08:06 51208 /tmp/hsperfdata_root/10943 2b6abb256000-2b6abb258000 rw-p 0001c000 08:06 851970 /lib64/ld-2.5.so 2b6abb258000-2b6abb26f000 r-xp 00000000 08:06 508048 /usr/lib64/libXmu.so.6.2.0 2b6abb26f000-2b6abb46f000 ---p 00017000 08:06 508048 /usr/lib64/libXmu.so.6.2.0 2b6abb46f000-2b6abb471000 rw-p 00017000 08:06 508048 /usr/lib64/libXmu.so.6.2.0 2b6abb471000-2b6abb4cc000 r-xp 00000000 08:06 507918 /usr/lib64/libXt.so.6.0.0 2b6abb4cc000-2b6abb6cc000 ---p 0005b000 08:06 507918 /usr/lib64/libXt.so.6.0.0 2b6abb6cc000-2b6abb6d2000 rw-p 0005b000 08:06 507918 /usr/lib64/libXt.so.6.0.0 2b6abb6d2000-2b6abb6d3000 rw-p 2b6abb6d2000 00:00 0 2b6abb6d3000-2b6abb6e3000 r-xp 00000000 08:06 507912 /usr/lib64/libXext.so.6.4.0 2b6abb6e3000-2b6abb8e2000 ---p 00010000 08:06 507912 /usr/lib64/libXext.so.6.4.0 2b6abb8e2000-2b6abb8e4000 rw-p 0000f000 08:06 507912 /usr/lib64/libXext.so.6.4.0 2b6abb8e4000-2b6abb8e5000 rw-p 2b6abb8e4000 00:00 0 2b6abb8e5000-2b6abba17000 r-xp 00000000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abba17000-2b6abbc17000 ---p 00132000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abbc17000-2b6abbc18000 r--p 00132000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abbc18000-2b6abbc1f000 rw-p 00133000 08:06 218719 /usr/lib64/libX11.so.6.2.0 2b6abbc1f000-2b6abbc28000 r-xp 00000000 08:06 217931 /usr/lib64/libSM.so.6.0.0 2b6abbc28000-2b6abbe28000 ---p 00009000 08:06 217931 /usr/lib64/libSM.so.6.0.0 2b6abbe28000-2b6abbe2a000 rw-p 00009000 08:06 217931 /usr/lib64/libSM.so.6.0.0 2b6abbe2a000-2b6abbe41000 r-xp 00000000 08:06 216934 /usr/lib64/libICE.so.6.3.0 2b6abbe41000-2b6abc040000 ---p 00017000 08:06 216934 /usr/lib64/libICE.so.6.3.0 2b6abc040000-2b6abc042000 rw-p 00016000 08:06 216934 /usr/lib64/libICE.so.6.3.0 2b6abc042000-2b6abc047000 rw-p 2b6abc042000 00:00 0 2b6abc047000-2b6abc193000 r-xp 00000000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc193000-2b6abc393000 ---p 0014c000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc393000-2b6abc399000 r--p 0014c000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc399000-2b6abc39b000 rw-p 00152000 08:06 985493 /root/2.0.3.1/CLHEP/libCLHEP-2.0.3.1.so 2b6abc39b000-2b6abc39e000 rw-p 2b6abc39b000 00:00 0 2b6abc39e000-2b6abca69000 r-xp 00000000 08:06 493498 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/libjvm.so 2b6abca69000-2b6abcb68000 ---p 006cb000 08:06 493498 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/libjvm.so 2b6abcb68000-2b6abcce3000 rw-p 006ca000 08:06 493498 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/server/libjvm.so 2b6abcce3000-2b6abcd12000 rw-p 2b6abcce3000 00:00 0 2b6abcd12000-2b6abcdf5000 r-xp 00000000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcdf5000-2b6abcff5000 ---p 000e3000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcff5000-2b6abcffb000 r--p 000e3000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcffb000-2b6abcffe000 rw-p 000e9000 08:06 217112 /usr/lib64/libstdc++.so.6.0.8 2b6abcffe000-2b6abd011000 rw-p 2b6abcffe000 00:00 0 2b6abd011000-2b6abd066000 r-xp 00000000 08:06 851985 /lib64/libm-2.5.so 2b6abd066000-2b6abd265000 ---p 00055000 08:06 851985 /lib64/libm-2.5.so 2b6abd265000-2b6abd267000 rw-p 00054000 08:06 851985 /lib64/libm-2.5.so 2b6abd267000-2b6abd274000 r-xp 00000000 08:06 852021 /lib64/libgcc_s.so.1 2b6abd274000-2b6abd473000 ---p 0000d000 08:06 852021 /lib64/libgcc_s.so.1 2b6abd473000-2b6abd475000 rw-p 0000c000 08:06 852021 /lib64/libgcc_s.so.1 2b6abd475000-2b6abd5ae000 r-xp 00000000 08:06 851977 /lib64/libc-2.5.so 2b6abd5ae000-2b6abd7ad000 ---p 00139000 08:06 851977 /lib64/libc-2.5.so 2b6abd7ad000-2b6abd7b0000 r--p 00138000 08:06 851977 /lib64/libc-2.5.so 2b6abd7b0000-2b6abd7b2000 rw-p 0013b000 08:06 851977 /lib64/libc-2.5.so 2b6abd7b2000-2b6abd7b8000 rw-p 2b6abd7b2000 00:00 0 2b6abd7b8000-2b6abd7bd000 r-xp 00000000 08:06 216938 /usr/lib64/libXdmcp.so.6.0.0 2b6abd7bd000-2b6abd9bc000 ---p 00005000 08:06 216938 /usr/lib64/libXdmcp.so.6.0.0 2b6abd9bc000-2b6abd9be000 rw-p 00004000 08:06 216938 /usr/lib64/libXdmcp.so.6.0.0 2b6abd9be000-2b6abd9d4000 r-xp 00000000 08:06 852003 /lib64/libpthread-2.5.so 2b6abd9d4000-2b6abdbd3000 ---p 00016000 08:06 852003 /lib64/libpthread-2.5.so 2b6abdbd3000-2b6abdbd5000 rw-p 00015000 08:06 852003 /lib64/libpthread-2.5.so 2b6abdbd5000-2b6abdbd9000 rw-p 2b6abdbd5000 00:00 0 2b6abdbd9000-2b6abdbdb000 r-xp 00000000 08:06 216936 /usr/lib64/libXau.so.6.0.0 2b6abdbdb000-2b6abddda000 ---p 00002000 08:06 216936 /usr/lib64/libXau.so.6.0.0 2b6abddda000-2b6abdddc000 rw-p 00001000 08:06 216936 /usr/lib64/libXau.so.6.0.0 2b6abdddc000-2b6abdddd000 rw-p 2b6abdddc000 00:00 0 2b6abdddd000-2b6abdddf000 r-xp 00000000 08:06 851983 /lib64/libdl-2.5.so 2b6abdddf000-2b6abdfdf000 ---p 00002000 08:06 851983 /lib64/libdl-2.5.so 2b6abdfdf000-2b6abdfe1000 rw-p 00002000 08:06 851983 /lib64/libdl-2.5.so 2b6abdfe1000-2b6abdfe3000 rw-p 2b6abdfe1000 00:00 0 2b6abdfe3000-2b6abdff7000 r-xp 00000000 08:06 851988 /lib64/libnsl-2.5.so 2b6abdff7000-2b6abe1f6000 ---p 00014000 08:06 851988 /lib64/libnsl-2.5.so 2b6abe1f6000-2b6abe1f8000 rw-p 00013000 08:06 851988 /lib64/libnsl-2.5.so 2b6abe1f8000-2b6abe1fa000 rw-p 2b6abe1f8000 00:00 0 2b6abe1fa000-2b6abe207000 r-xp 00000000 08:06 493489 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so 2b6abe207000-2b6abe306000 ---p 0000d000 08:06 493489 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so 2b6abe306000-2b6abe309000 rw-p 0000c000 08:06 493489 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libverify.so 2b6abe309000-2b6abe32e000 r-xp 00000000 08:06 493474 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so 2b6abe32e000-2b6abe42d000 ---p 00025000 08:06 493474 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so 2b6abe42d000-2b6abe433000 rw-p 00024000 08:06 493474 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libjava.so 2b6abe433000-2b6abe442000 r-xp 00000000 08:06 493490 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so 2b6abe442000-2b6abe543000 ---p 0000f000 08:06 493490 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so 2b6abe543000-2b6abe547000 rw-p 00010000 08:06 493490 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/amd64/libzip.so 2b6abe547000-2b6ac0b5d000 r--s 00000000 08:06 493583 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/rt.jar 2b6ac0b5d000-2b6ac0bc6000 rw-p 2b6ac0b5d000 00:00 0 2b6ac0bc6000-2b6ac0c4b000 r--s 00000000 08:06 493566 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/jsse.jar 2b6ac0c4b000-2b6ac0c60000 r--s 00000000 08:06 493565 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/jce.jar 2b6ac0c60000-2b6ac14d0000 r--s 00000000 08:06 493504 /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update8/jre/lib/charsets.jar 2b6ac14d0000-2b6ac1740000 rwxp 2b6ac14d0000 00:00 0 2b6ac1740000-2b6ac44d0000 rwxp 2b6ac1740000 00:00 0 2b6ac44d0000-2b6ac44da000 rwxp 2b6ac44d0000 00:00 0 2b6ac44da000-2b6ac4590000 rwxp 2b6ac44da000 00:00 0 2b6ac4590000-2b6ac5a50000 rwxp 2b6ac4590000 00:00 0 2b6ac5a50000-2b6ac9790000 rwxp 2b6ac5a50000 00:00 0 2b6ac9790000-2b6acac90000 rwxp 2b6ac9790000 00:00 0 2b6acac90000-2b6ade790000 rwxp 2b6acac90000 00:00 0 2b6ade790000-2b6adf9f0000 rwxp 2b6ade790000 00:00 0 2b6adf9f0000-2b6ae8f90000 rwxp 2b6adf9f0000 00:00 0 2b6ae8f90000-2b6ae8f9b000 rwxp 2b6ae8f90000 00:00 0 2b6ae8f9b000-2b6ae8fb9000 rwxp 2b6ae8f9b000 00:00 0 2b6ae8fb9000-2b6ae8fc4000 rwxp 2b6ae8fb9000 00:00 0 2b6ae8fc4000-2b6ae9061000 rwxp 2b6ae8fc4000 00:00 0 2b6ae9061000-2b6ae906b000 rwxp 2b6ae9061000 00:00 0 2b6ae906b000-2b6ae90b5000 rwxp 2b6ae906b000 00:00 0 2b6ae90b5000-2b6ae90c1000 rwxp 2b6ae90b5000 00:00 0 2b6ae90c1000-2b6ae915e000 rwxp 2b6ae90c1000 00:00 0 2b6ae915e000-2b6ae9169000 rwxp 2b6ae915e000 00:00 0 2b6ae9169000-2b6ae9187000 rwxp 2b6ae9169000 00:00 0 7fffef86d000-7fffef870000 ---p 7fffef86d000 00:00 0 7fffef870000-7fffefa6d000 rwxp 7fffef870000 00:00 0 [stack] 7fffefa6d000-7fffefa70000 rw-p 7fffefa6d000 00:00 0 ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso] VM Arguments: java_command: <unknown> Launcher Type: generic Environment Variables: JAVA_HOME=/usr/lib64/jvm/java JRE_HOME=/usr/lib64/jvm/java/jre PATH=/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/aidajni-3.2.6/bin/amd64-Linux-g++:/root/aidajni-3.2.6/bin/amd64-Linux-g++:/sbin:/usr/sbin:/usr/local/sbin:/opt/kde3/sbin:/opt/gnome/sbin:/root/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/lib/qt3/bin:/home/G4Workdir/bin/Linux-g++:/home/G4Workdir/bin/Linux-g++:/home/G4Workdir/bin/Linux-g++ LD_LIBRARY_PATH=/usr/lib64/jvm/java/jre/lib/amd64:/usr/lib64/jvm/java/jre/lib/amd64/server:/root/aidajni-3.2.6/lib/amd64-Linux-g++:/root/2.0.3.1/CLHEP SHELL=/bin/bash DISPLAY=:0.0 HOSTTYPE=x86_64 OSTYPE=linux MACHTYPE=x86_64-suse-linux Signal Handlers: SIGSEGV: [libjvm.so+0x656380], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGBUS: [libjvm.so+0x656380], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGFPE: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGPIPE: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGILL: [libjvm.so+0x55dd50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGUSR1: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000 SIGUSR2: [libjvm.so+0x55fc00], sa_mask[0]=0x00000000, sa_flags=0x14000004 SIGHUP: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGINT: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGQUIT: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 SIGTERM: [libjvm.so+0x55f6d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004 --------------- S Y S T E M --------------- OS:openSUSE 10.2 (X86-64) VERSION = 10.2 uname:Linux 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 x86_64 libc:glibc 2.5 NPTL 2.5 rlimit: STACK 8192k, CORE 0k, NPROC 16382, NOFILE 8192, AS 2882320k load average:0.41 0.27 0.20 CPU:total 2 em64t ht Memory: 4k page, physical 2060636k(907992k free), swap 1542200k(1542200k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03) for linux-amd64, built on Jun 28 2006 00:27:03 by java_re with gcc 3.2.2 (SuSE Linux)

Re: Aida and exA01 on x86_64 by Mark Donszelmann <Mark Donszelmann>, 03 May, 2007
Re: Aida and exA01 on x86_64 (Theo)

Hi which download of AIDAJNI did you use? Regards Mark On May 3, 2007, at 12:03 PM, Theo wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/281"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Dear all > > i have suse 10.2 64bit and just installed geant4.after installing > jaida > and aidajni tried to run example A01 (after compiling it > successfully) > and got this message which i have no idea what it means. > > An unexpected error has been detected by HotSpot Virtual Machine: > > # > # SIGSEGV (0xb) at pc=0x00002b758b0191b6, pid=6235, > tid=47783893238560 > # > # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_08-b03 mixed mode) > # Problematic frame: > # C [ld-linux-x86-64.so.2+0x91b6] > # > # An error report file with more information is saved as > hs_err_pid6235.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > > Aborted > > Any ideas?Thanks in advance. theo

run01.mac file needed for TestEm4 by Victor_Makarov <Victor_Makarov>, 28 Apr, 2007 I find no such file in my example directory. Perhaps, it's because someone forgot to add it in 4.8.2 version of Giant. I would be thankful for the file.

Re: run01.mac file needed for TestEm4 by michel maire <michel maire>, 29 Apr, 2007 Re: run01.mac file needed for TestEm4 (Victor_Makarov) User Victor wrote: >> I find no such file in my example directory. Perhaps, it's because >> someone forgot to add it in 4.8.2 version of Giant. I would be thankful >> for the file. take Testem4.in Michel

Re: run01.mac file needed for TestEm4 by Victor_Makarov <Victor_Makarov>, 29 Apr, 2007 Re: Re: run01.mac file needed for TestEm4 (michel maire) But it calls no historgams...

Re: run01.mac file needed for TestEm4 by michel maire <michel maire>, 02 May, 2007 Re: Re: run01.mac file needed for TestEm4 (Victor_Makarov) User Victor wrote: >> But it calls no historgams... In Em4, it is enough to activate G4ANALYSIS_USE to fill the histogram -only one- booked in RunAction.

Re: run01.mac file needed for TestEm4 by Victor_Makarov <Victor_Makarov>, 05 May, 2007 Re: Re: run01.mac file needed for TestEm4 (michel maire) Thanx, I've got it..

linking error of example A01 Keywords: linking error,AIDA
by long <long>, 25 Apr, 2007

Dear Geatn4 experts, When I tried to compile exampleA01, I met linking error as follows. My geant4 is 8.2., aidajni-3.2.6 ,jaida-3.3.0-2. JRE1.5.0. The error information: Using granular libraries ... Linking A01app ... /home/aidajni-3.2.6/lib/i386-Linux-g++/libfreehep-aidajni-3.2.6.a(ProxyFactory.o): In function `std::__simple_alloc<std::_Rb_tree_node<std::pair<long long const, void const*> >, std::__default_alloc_template<true, 0> >::allocate(unsigned int)': ProxyFactory.cpp:(.gnu.linkonce.t._ZNSt14__simple_allocISt13_Rb_tree_nodeISt4pairIKxPKvEESt24__default_alloc_templateILb1ELi0EEE8allocateEj+0x25): undefined reference to `std::__default_alloc_template<true, 0>::allocate(unsigned int)' ........................... ........................... ........................... JIFitData.cpp:(.gnu.linkonce.t._ZNSt14__simple_allocISt13_Rb_tree_nodeISt4pairIKiPN4AIDA9IRangeSetEEESt24__default_alloc_templateILb1ELi0EEE10deallocateEPS7_j+0x24): undefined reference to `std::__default_alloc_template<true, 0>::deallocate(void*, unsigned int)' /home/aidajni-3.2.6/lib/i386-Linux-g++/libfreehep-aidajni-3.2.6.a(JIFitData.o): In function `std::__simple_alloc<std::_Rb_tree_node<std::pair<int const, AIDA::IRangeSet*> >, std::__default_alloc_template<true, 0> >::allocate(unsigned int)': JIFitData.cpp:(.gnu.linkonce.t._ZNSt14__simple_allocISt13_Rb_tree_nodeISt4pairIKiPN4AIDA9IRangeSetEEESt24__default_alloc_templateILb1ELi0EEE8allocateEj+0x28): undefined reference to `std::__default_alloc_template<true, 0>::allocate(unsigned int)' collect2: ld returned 1 exit status make: *** [/home/work/gwork/bin/Linux-g++/A01app] Error 1 Some enviroment variable have been set: AIDAJNI_HOME=/home/aidajni-3.2.6 AIDAJNI_LIBS=-L/home/aidajni-3.2.6/lib/i386-Linux-g++ -lfreehep-aidajni-3.2.6 -L/opt/jdk1.6.0_01/jre/lib/i386/client -ljvm AIDAJNI_NAME=freehep-aidajni-3.2.6 AIDAJNI_VERSION=3.2.6 AIDAJNI_INCLUDES=-I/home/aidajni-3.2.6/include AIDAJNI_AOL=i386-Linux-g++ JAIDA_HOME=/home/jaida-3.3.0-2 Could you tell me how to solve this problem? Thank you very much! -long

linking error of example A01 Keywords: linking error, A01, AIDA, AIDAJNI by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 27 Sep, 2007 Re: linking error of example A01 (long) Hello ! I have exactly the same linking error as the previous message, with the extended example A01. I have Geant4.9.0, JAIDA-3.2.4, aidajni-3.2.6. My related environment variables are: AIDAJNI_HOME=/home/kshtejer/local/aidajni-3.2.6 AIDAJNI_LIBS=-L/home/kshtejer/local/aidajni-3.2.6/lib/i386-Linux-g++ -lfreehep-aidajni-3.2.6 -L/usr/lib/j2se/1.4/jre/lib/i386/client -ljvm AIDAJNI_NAME=freehep-aidajni-3.2.6 AIDAJNI_VERSION=3.2.6 AIDAJNI_INCLUDES=-I/home/kshtejer/local/aidajni-3.2.6/include AIDAJNI_AOL=i386-Linux-g++ JAIDA_HOME=/home/kshtejer/local/JAIDA-3.2.4 JDK_HOME=/usr/lib/j2se/1.4 I decided to install the newer version of AIDAJNI, because it was the only solution I found to avoid the following link error always appearing with the previous versions: /usr/bin/ld: warning: libstdc++.so.5, needed by /home/kshtejer/bin/AIDAJNI-3.2.3/lib/Linux- g++/libAIDAJNI.so, may conflict with libstdc++.so.6 Now, I do not know what is exactly the problem and what to do to solve this. I would appreciate any help, Thank you very much, Katherin

Re: linking error of example A01 by Mark Donszelmann <Mark Donszelmann>, 27 Sep, 2007
Re: linking error of example A01 (Katherin Shtejer Diaz)

Hi which platform are you on ? Architecture, OS, g++ version. Regards Mark On Sep 27, 2007, at 3:13 AM, Katherin Shtejer Diaz wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/277/1"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Hello ! > > I have exactly the same linking error as the previous message, with > the extended example A01. > I have Geant4.9.0, JAIDA-3.2.4, aidajni-3.2.6. > > My related environment variables are: > > AIDAJNI_HOME=/home/kshtejer/local/aidajni-3.2.6 > AIDAJNI_LIBS=-L/home/kshtejer/local/aidajni-3.2.6/lib/i386-Linux-g+ > + -lfreehep-aidajni-3.2.6 -L/usr/lib/j2se/1.4/jre/lib/i386/client - > ljvm > AIDAJNI_NAME=freehep-aidajni-3.2.6 > AIDAJNI_VERSION=3.2.6 > AIDAJNI_INCLUDES=-I/home/kshtejer/local/aidajni-3.2.6/include > AIDAJNI_AOL=i386-Linux-g++ > JAIDA_HOME=/home/kshtejer/local/JAIDA-3.2.4 > JDK_HOME=/usr/lib/j2se/1.4 > > I decided to install the newer version of AIDAJNI, because it was > the only solution I found to > avoid the following link error always appearing with the previous > versions: > > /usr/bin/ld: warning: libstdc++.so.5, needed by /home/kshtejer/bin/ > AIDAJNI-3.2.3/lib/Linux- g++/libAIDAJNI.so, may conflict with > libstdc++.so.6 > > Now, I do not know what is exactly the problem and what to do to > solve this. > > I would appreciate any help, > > Thank you very much, > > Katherin >

Re: linking error of example A01 by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 27 Sep, 2007 Re: Re: linking error of example A01 (Mark Donszelmann) Hi, I am working on: i686 GNU/Linux g++ 4.1.2 (Ubuntu) Regards, Katherin

Re: linking error of example A01 by Mark Donszelmann <Mark Donszelmann>, 27 Sep, 2007
Re: Re: linking error of example A01 (Katherin Shtejer Diaz)

Hi you could try to recompile AIDAJNI as per instructions on http://java.freehep.org/aidajni/BuildFromSource.html on your platform. It helped the previous bug submitter, but he was on some different architecture. Regards Mark On Sep 27, 2007, at 7:31 AM, Katherin Shtejer Diaz wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/277/1/1/1"@geant4-hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Hi, > > I am working on: > > i686 GNU/Linux g++ 4.1.2 (Ubuntu) > > Regards, > > Katherin

Re: linking error of example A01 by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 27 Sep, 2007 Re: Re: linking error of example A01 (Mark Donszelmann) ...yes, I tried to recompiled the source AIDAJNI-3.2.0.2-src.tar.gz, following the instructions of the README-src file, but at a certain point, with the instruction: tools/ant -Djar=aidajni I obtained this: "bash: tools/ant: No such file or directory" So, I am sorry for my few Java knowledges, but I didn't know how to proceed. I need any advice on this. I would really appreciate, because I need to solve this problem of the aidajni installation to continue. Regards Katherin

Re:Now A01 links but does not run Keywords: A01, error at run time
by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 15 Oct, 2007
Re: Re: linking error of example A01 (Katherin Shtejer Diaz)

Hello again, Finally I have successfully built the AIDAJNI-3.2.3 from the source and compiled the extended example A01, using JAIDA-3.2.3 and AIDAJNI-3.2.3. It compiled and linked OK!!! But the running process aborted with the following message: ********************************************** Local Time = Mon Oct 15 13:05:39 2007 Elapsed Time = 2 # # The exception above was detected in native code outside the VM # # Java VM: Java HotSpot(TM) Client VM (Blackdown-1.4.2-02 mixed mode) # # An error report file has been saved as hs_err_pid32607.log. # Please refer to the file for further information. # Aborted (core dumped) ********************************************** I am using Ubuntu. I would like to remark that I have done the same installation of Geant4.9.0 under Scientific Linux 4.5, in other computer and the same problem is happening related to jaida-aidajni (compiled from the source) when running the example A01. Please, I would appreciate any idea to solve this problem. Here I am posting the log error report file. Maybe it could be usefull. Than you in advance, Katherin The log file: An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0xA98BE98A Function=_XmGetFocusData+0x72 Library=/usr/lib/j2se/1.4/jre/lib/i386/libXm.so.3 Current Java thread: at sun.awt.motif.MWindowPeer.pCreate(Native Method) at sun.awt.motif.MWindowPeer.create(MWindowPeer.java:79) at sun.awt.motif.MComponentPeer.init(MComponentPeer.java:222) at sun.awt.motif.MWindowPeer.init(MWindowPeer.java:90) at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:58) at sun.awt.motif.MToolkit.createFrame(MToolkit.java:209) at java.awt.Frame.addNotify(Frame.java:472) - locked <0xaa85d710> (a java.awt.Component$AWTTreeLock) at java.awt.Window.pack(Window.java:436) at hep.aida.ref.plotter.Plotter.show(Plotter.java:74) Dynamic libraries: 08048000-0804d000 r-xp 00000000 08:05 4900458 /home/kshtejer/CERN/work/g4work/bin/Linux-g++/A01app 0804d000-0804e000 rw-p 00004000 08:05 4900458 /home/kshtejer/CERN/work/g4work/bin/Linux-g++/A01app 0804e000-0854a000 rw-p 0804e000 00:00 0 [heap] a9590000-a9596000 r--s 00000000 08:05 1343580 /var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-x86.cache-2 a9596000-a9597000 r--s 00000000 08:05 1344044 /var/cache/fontconfig/fd9505950c048a77dc4b710eb6a628ed-x86.cache-2 a9597000-a959a000 r--s 00000000 08:05 1344043 /var/cache/fontconfig/ddc79d3ea06a7c6ffa86ede85f3bb5df-x86.cache-2 a959a000-a959b000 r--s 00000000 08:05 1344042 /var/cache/fontconfig/e7071f4a29fa870f4323321c154eba04-x86.cache-2 a959b000-a959c000 r--s 00000000 08:05 1344041 /var/cache/fontconfig/a2ab74764b07279e7c36ddb1d302cf26-x86.cache-2 a959c000-a95a0000 r--s 00000000 08:05 1343577 /var/cache/fontconfig/921a30a17f0be15c70ac14043cb7a739-x86.cache-2 a95a0000-a95a1000 r--s 00000000 08:05 1344039 /var/cache/fontconfig/4c73fe0c47614734b17d736dbde7580a-x86.cache-2 a95a1000-a95a3000 r--s 00000000 08:05 1344038 /var/cache/fontconfig/646addb8444faa74ee138aa00ab0b6a0-x86.cache-2 a95a3000-a95a5000 r--s 00000000 08:05 1344037 /var/cache/fontconfig/20bd79ad97094406f7d1b9654bfbd926-x86.cache-2 a95a5000-a95a6000 r--s 00000000 08:05 1344036 /var/cache/fontconfig/75a2cd575a62c63e802c11411fb87c37-x86.cache-2 a95a6000-a95a8000 r--s 00000000 08:05 1344035 /var/cache/fontconfig/9c0624108b9a2ae8552f664125be8356-x86.cache-2 a95a8000-a95ae000 r--s 00000000 08:05 1344034 /var/cache/fontconfig/6d41288fd70b0be22e8c3a91e032eec0-x86.cache-2 a95ae000-a95b0000 r--s 00000000 08:05 1344033 /var/cache/fontconfig/de156ccd2eddbdc19d37a45b8b2aac9c-x86.cache-2 a95b0000-a95b2000 r--s 00000000 08:05 1344032 /var/cache/fontconfig/da1bd5ca8443ffe22927a23ce431d198-x86.cache-2 a95b2000-a95ba000 r--s 00000000 08:05 1344031 /var/cache/fontconfig/e3de0de479f42330eadf588a55fb5bf4-x86.cache-2 a95ba000-a95c0000 r--s 00000000 08:05 1344030 /var/cache/fontconfig/0f34bcd4b6ee430af32735b75db7f02b-x86.cache-2 a95c0000-a95c1000 r--s 00000000 08:05 1344054 /var/cache/fontconfig/9451a55048e8dbe8633e64d34165fdf2-x86.cache-2 a95c1000-a95c2000 r--s 00000000 08:05 1344029 /var/cache/fontconfig/4794a0821666d79190d59a36cb4f44b5-x86.cache-2 a95c2000-a95c4000 r--s 00000000 08:05 1344351 /var/cache/fontconfig/2c5ba8142dffc8bf0377700342b8ca1a-x86.cache-2 a95c4000-a95c6000 r--s 00000000 08:05 1344028 /var/cache/fontconfig/de9486f0b47a4d768a594cb4198cb1c6-x86.cache-2 a95c6000-a95cc000 r--s 00000000 08:05 1344027 /var/cache/fontconfig/d52a8644073d54c13679302ca1180695-x86.cache-2 a95cc000-a95d0000 r--s 00000000 08:05 1344050 /var/cache/fontconfig/105b9c7e6f0a4f82d8c9b6e39c52c6f9-x86.cache-2 a95d0000-a95d3000 r--s 00000000 08:05 1344026 /var/cache/fontconfig/6386b86020ecc1ef9690bb720a13964f-x86.cache-2 a95d3000-a95d7000 r--s 00000000 08:05 1343562 /var/cache/fontconfig/089dead882dea3570ffc31a9898cfb69-x86.cache-2 a95d7000-a95de000 r--s 00000000 08:05 1344789 /var/cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-x86.cache-2 a95de000-a95df000 r--s 00000000 08:05 1344069 /var/cache/fontconfig/fcff1cd55d48a2c86a175e9943c3506d-x86.cache-2 a95df000-a95e1000 r--s 00000000 08:05 1344741 /var/cache/fontconfig/e9e44584608a73233979f764b5f9dd81-x86.cache-2 a95e1000-a95e2000 r--s 00000000 08:05 1344067 /var/cache/fontconfig/b5a4f3f568a71026ccdc6a3a51afa9b4-x86.cache-2 a95e2000-a95e3000 r--s 00000000 08:05 1344739 /var/cache/fontconfig/e22b663d51a3e226824aa2afd6c591f7-x86.cache-2 a95e3000-a95e4000 r--s 00000000 08:05 1344066 /var/cache/fontconfig/2561679576a9c7fd2ce41d281d4e00d1-x86.cache-2 a95e4000-a95e5000 r--s 00000000 08:05 1344349 /var/cache/fontconfig/bf1f9632594a1fa28e2cf4d7888deffe-x86.cache-2 a95e5000-a95e6000 r--s 00000000 08:05 1344065 /var/cache/fontconfig/b8613a33de00eecd32d5a94c3c617829-x86.cache-2 a95e6000-a95e9000 r--s 00000000 08:05 1344064 /var/cache/fontconfig/b21a91cee725896328b8cee8091cf747-x86.cache-2 a95e9000-a95ee000 r--s 00000000 08:05 1344063 /var/cache/fontconfig/fd9416c4b92f07c6f59a3a8cf496e9dc-x86.cache-2 a95ee000-a95f0000 r--s 00000000 08:05 1344357 /var/cache/fontconfig/059138ec877db160474b4d5de1248d14-x86.cache-2 a95f0000-a95f1000 r--s 00000000 08:05 1344061 /var/cache/fontconfig/f5a93ac943883aa0fd9a7bfe0f6ec3c1-x86.cache-2 a95f1000-a95f3000 r--s 00000000 08:05 1344356 /var/cache/fontconfig/118d8d5311348bbdf5fe3b106d7c13d4-x86.cache-2 a95f3000-a95f4000 r--s 00000000 08:05 1344059 /var/cache/fontconfig/a1131b7be650f9abae4907495aa5815d-x86.cache-2 a95f4000-a95f9000 r--s 00000000 08:05 1344058 /var/cache/fontconfig/8ab5f685cd6d8ba67c37c908faf08172-x86.cache-2 a95f9000-a95fd000 r--s 00000000 08:05 1344355 /var/cache/fontconfig/0f32d3adc6a232110812e17374eaa446-x86.cache-2 a95fd000-a95ff000 r--s 00000000 08:05 1344056 /var/cache/fontconfig/7b4a97c10f6c0166998ddfa1cf7392fb-x86.cache-2 a95ff000-a9602000 r--s 00000000 08:05 1344055 /var/cache/fontconfig/61c830dfac3fd78a12654da5e9ba3f56-x86.cache-2 a9602000-a9603000 r--s 00000000 08:05 1344354 /var/cache/fontconfig/e0f9e95429e756d56293ed4d63866094-x86.cache-2 a9603000-a9605000 r--s 00000000 08:05 1344053 /var/cache/fontconfig/4123634e9c08547d899d0aaff05ebe69-x86.cache-2 a9605000-a9609000 r--s 00000000 08:05 1344052 /var/cache/fontconfig/142ecfc435bad6f1fbc2648c1119d5eb-x86.cache-2 a9609000-a960f000 r--s 00000000 08:05 1344051 /var/cache/fontconfig/102e5142c2e9e50c5e8ece26694a2dad-x86.cache-2 a96aa000-a96ae000 r-xp 00000000 08:05 132363 /usr/lib/libXfixes.so.3.1.0 a96ae000-a96af000 rw-p 00003000 08:05 132363 /usr/lib/libXfixes.so.3.1.0 a96af000-a96b6000 r-xp 00000000 08:05 132383 /usr/lib/libXrender.so.1.3.0 a96b6000-a96b7000 rw-p 00006000 08:05 132383 /usr/lib/libXrender.so.1.3.0 a96b7000-a96bf000 r-xp 00000000 08:05 132353 /usr/lib/libXcursor.so.1.0.2 a96bf000-a96c0000 rw-p 00007000 08:05 132353 /usr/lib/libXcursor.so.1.0.2 a96d9000-a9776000 r-xp 00000000 08:05 805035 /usr/lib/j2se/1.4/jre/lib/i386/libfontmanager.so a9776000-a9788000 rw-p 0009d000 08:05 805035 /usr/lib/j2se/1.4/jre/lib/i386/libfontmanager.so a978c000-a9790000 r-xp 00000000 08:05 132389 /usr/lib/libXtst.so.6.1.0 a9790000-a9791000 rw-p 00003000 08:05 132389 /usr/lib/libXtst.so.6.1.0 a9791000-a9798000 r-xp 00000000 08:05 132377 /usr/lib/libXp.so.6.2.0 a9798000-a9799000 rw-p 00006000 08:05 132377 /usr/lib/libXp.so.6.2.0 a9799000-a97a3000 r--s 00000000 08:05 1344352 /var/cache/fontconfig/a960c40fc9306f090224a04585f8a963-x86.cache-2 a97a3000-a97a5000 r--s 00000000 08:05 1344048 /var/cache/fontconfig/9404ff413c67fc2a1526fd14eb4163a8-x86.cache-2 a97a5000-a97a9000 r--s 00000000 08:05 1344350 /var/cache/fontconfig/b3fedf7c409f006ca1a6fceffceb77cf-x86.cache-2 a97a9000-a97ab000 r--s 00000000 08:05 1343592 /var/cache/fontconfig/6330322105e0c4105d7c7a6ea2974107-x86.cache-2 a97ab000-a97b2000 r--s 00000000 08:05 1344788 /var/cache/fontconfig/beeeeb3dfe132a8a0633a017c99ce0c0-x86.cache-2 a97b2000-a99a4000 r-xp 00000000 08:05 805019 /usr/lib/j2se/1.4/jre/lib/i386/libXm.so.3 a99a4000-a99be000 rw-p 001f1000 08:05 805019 /usr/lib/j2se/1.4/jre/lib/i386/libXm.so.3 a99bf000-a9a25000 r-xp 00000000 08:05 805016 /usr/lib/j2se/1.4/jre/lib/i386/libmlib_image.so a9a25000-a9a26000 rw-p 00066000 08:05 805016 /usr/lib/j2se/1.4/jre/lib/i386/libmlib_image.so a9a26000-a9b07000 r-xp 00000000 08:05 805027 /usr/lib/j2se/1.4/jre/lib/i386/libawt.so a9b07000-a9b10000 rw-p 000e0000 08:05 805027 /usr/lib/j2se/1.4/jre/lib/i386/libawt.so a9b34000-a9b3c000 r--s 00000000 08:05 5390487 /home/kshtejer/local/JAIDA-3.2.3/lib/aida.jar a9b3c000-a9bbb000 r--s 00000000 08:05 5390492 /home/kshtejer/local/JAIDA-3.2.3/lib/bcel.jar a9bbb000-a9c6d000 r--s 00000000 08:05 5390490 /home/kshtejer/local/JAIDA-3.2.3/lib/freehep-base.jar a9c6d000-a9d77000 r--s 00000000 08:05 5390489 /home/kshtejer/local/JAIDA-3.2.3/lib/freehep-hep.jar a9d77000-a9e0e000 r--s 00000000 08:05 5390495 /home/kshtejer/local/JAIDA-3.2.3/lib/jas-plotter.jar a9e0e000-a9e17000 r--s 00000000 08:05 5390493 /home/kshtejer/local/JAIDA-3.2.3/lib/jel.jar a9e17000-a9e27000 r--s 00000000 08:05 5390491 /home/kshtejer/local/JAIDA-3.2.3/lib/openide-lookup.jar a9e27000-a9e33000 r--s 00000000 08:05 5390494 /home/kshtejer/local/JAIDA-3.2.3/lib/optimizers.jar a9e33000-a9e38000 r--s 00000000 08:05 5391259 /home/kshtejer/local/AIDAJNI-3.2.3/lib/freehep-aidajni.jar a9e38000-a9e54000 r--s 00000000 08:05 937615 /usr/lib/j2se/1.4/jre/lib/ext/sunjce_provider.jar a9e54000-a9f10000 r--s 00000000 08:05 937617 /usr/lib/j2se/1.4/jre/lib/ext/localedata.jar a9f10000-a9f1e000 r--s 00000000 08:05 937616 /usr/lib/j2se/1.4/jre/lib/ext/ldapsec.jar aa122000-aa15d000 r--p 00000000 08:05 197923 /usr/lib/locale/en_US.utf8/LC_CTYPE b2361000-b2364000 r--s 00000000 08:05 937614 /usr/lib/j2se/1.4/jre/lib/ext/dnsns.jar b440c000-b49ac000 r--s 00000000 08:05 512694 /usr/lib/j2se/1.4/jre/lib/charsets.jar b49ac000-b49bd000 r--s 00000000 08:05 512692 /usr/lib/j2se/1.4/jre/lib/jce.jar b49bd000-b4a9a000 r--s 00000000 08:05 512690 /usr/lib/j2se/1.4/jre/lib/jsse.jar b4a9a000-b4ab0000 r--s 00000000 08:05 512696 /usr/lib/j2se/1.4/jre/lib/sunrsasign.jar b4afa000-b64a6000 r--s 00000000 08:05 512697 /usr/lib/j2se/1.4/jre/lib/rt.jar b64a6000-b64b7000 r-xp 00000000 08:05 805023 /usr/lib/j2se/1.4/jre/lib/i386/libzip.so b64b7000-b64b9000 rw-p 00011000 08:05 805023 /usr/lib/j2se/1.4/jre/lib/i386/libzip.so b64b9000-b64d8000 r-xp 00000000 08:05 805013 /usr/lib/j2se/1.4/jre/lib/i386/libjava.so b64d8000-b64d9000 rw-p 0001f000 08:05 805013 /usr/lib/j2se/1.4/jre/lib/i386/libjava.so b64d9000-b64e2000 r-xp 00000000 08:05 5588243 /lib/tls/i686/cmov/libnss_files-2.5.so b64e2000-b64e4000 rw-p 00008000 08:05 5588243 /lib/tls/i686/cmov/libnss_files-2.5.so b64e4000-b64ec000 r-xp 00000000 08:05 5588247 /lib/tls/i686/cmov/libnss_nis-2.5.so b64ec000-b64ee000 rw-p 00007000 08:05 5588247 /lib/tls/i686/cmov/libnss_nis-2.5.so b64ee000-b64f5000 r--s 00000000 08:05 4866283 /usr/lib/gconv/gconv-modules.cache b64f5000-b6506000 r-xp 00000000 08:05 805015 /usr/lib/j2se/1.4/jre/lib/i386/libverify.so b6506000-b6507000 rw-p 00011000 08:05 805015 /usr/lib/j2se/1.4/jre/lib/i386/libverify.so b650c000-b651f000 r-xp 00000000 08:05 5588237 /lib/tls/i686/cmov/libnsl-2.5.so b651f000-b6521000 rw-p 00012000 08:05 5588237 /lib/tls/i686/cmov/libnsl-2.5.so b6523000-b6527000 r-xp 00000000 08:05 132357 /usr/lib/libXdmcp.so.6.0.0 b6527000-b6528000 rw-p 00003000 08:05 132357 /usr/lib/libXdmcp.so.6.0.0 b6528000-b652a000 r-xp 00000000 08:05 132346 /usr/lib/libXau.so.6.0.0 b652a000-b652b000 rw-p 00001000 08:05 132346 /usr/lib/libXau.so.6.0.0 b652b000-b6533000 r-xp 00000000 08:05 132506 /usr/lib/libdrm.so.2.3.0 b6533000-b6534000 rw-p 00008000 08:05 132506 /usr/lib/libdrm.so.2.3.0 b6534000-b6536000 r-xp 00000000 08:05 5588232 /lib/tls/i686/cmov/libdl-2.5.so b6536000-b6538000 rw-p 00001000 08:05 5588232 /lib/tls/i686/cmov/libdl-2.5.so b6539000-b654c000 r-xp 00000000 08:05 5588252 /lib/tls/i686/cmov/libpthread-2.5.so b654c000-b654e000 rw-p 00013000 08:05 5588252 /lib/tls/i686/cmov/libpthread-2.5.so b6550000-b6554000 r-xp 00000000 08:05 132397 /usr/lib/libXxf86vm.so.1.0.0 b6554000-b6555000 rw-p 00003000 08:05 132397 /usr/lib/libXxf86vm.so.1.0.0 b6556000-b6691000 r-xp 00000000 08:05 5588226 /lib/tls/i686/cmov/libc-2.5.so b6691000-b6692000 r--p 0013b000 08:05 5588226 /lib/tls/i686/cmov/libc-2.5.so b6692000-b6694000 rw-p 0013c000 08:05 5588226 /lib/tls/i686/cmov/libc-2.5.so b6697000-b66a2000 r-xp 00000000 08:05 5554240 /lib/libgcc_s.so.1 b66a2000-b66a3000 rw-p 0000a000 08:05 5554240 /lib/libgcc_s.so.1 b66a3000-b66c8000 r-xp 00000000 08:05 5588234 /lib/tls/i686/cmov/libm-2.5.so b66c8000-b66ca000 rw-p 00024000 08:05 5588234 /lib/tls/i686/cmov/libm-2.5.so b66ca000-b67a9000 r-xp 00000000 08:05 133037 /usr/lib/libstdc++.so.6.0.8 b67a9000-b67ac000 r--p 000de000 08:05 133037 /usr/lib/libstdc++.so.6.0.8 b67ac000-b67ae000 rw-p 000e1000 08:05 133037 /usr/lib/libstdc++.so.6.0.8 b67b5000-b6a76000 r-xp 00000000 08:05 937633 /usr/lib/j2se/1.4/jre/lib/i386/client/libjvm.so b6a76000-b6a91000 rw-p 002c0000 08:05 937633 /usr/lib/j2se/1.4/jre/lib/i386/client/libjvm.so b6aa8000-b6aaa000 r-xp 00000000 08:05 5391258 /home/kshtejer/local/AIDAJNI-3.2.3/lib/Linux-g++/libFHJNI.so b6aaa000-b6aab000 rw-p 00001000 08:05 5391258 /home/kshtejer/local/AIDAJNI-3.2.3/lib/Linux-g++/libFHJNI.so b6aab000-b6bc2000 r-xp 00000000 08:05 5391254 /home/kshtejer/local/AIDAJNI-3.2.3/lib/Linux-g++/libAIDAJNI.so b6bc2000-b6bcf000 rw-p 00116000 08:05 5391254 /home/kshtejer/local/AIDAJNI-3.2.3/lib/Linux-g++/libAIDAJNI.so b6bcf000-b6d13000 r-xp 00000000 08:05 4620909 /home/kshtejer/CERN/alice/clhep/lib/libCLHEP-2.0.3.1.so b6d13000-b6d17000 rw-p 00144000 08:05 4620909 /home/kshtejer/CERN/alice/clhep/lib/libCLHEP-2.0.3.1.so b6d19000-b6d2e000 r-xp 00000000 08:05 132318 /usr/lib/libICE.so.6.3.0 b6d2e000-b6d30000 rw-p 00014000 08:05 132318 /usr/lib/libICE.so.6.3.0 b6d32000-b6d3a000 r-xp 00000000 08:05 132336 /usr/lib/libSM.so.6.0.0 b6d3a000-b6d3b000 rw-p 00007000 08:05 132336 /usr/lib/libSM.so.6.0.0 b6d3b000-b6e28000 r-xp 00000000 08:05 132340 /usr/lib/libX11.so.6.2.0 b6e28000-b6e2c000 rw-p 000ed000 08:05 132340 /usr/lib/libX11.so.6.2.0 b6e2c000-b6e39000 r-xp 00000000 08:05 132361 /usr/lib/libXext.so.6.4.0 b6e39000-b6e3a000 rw-p 0000d000 08:05 132361 /usr/lib/libXext.so.6.4.0 b6e3a000-b6e87000 r-xp 00000000 08:05 132387 /usr/lib/libXt.so.6.0.0 b6e87000-b6e8b000 rw-p 0004c000 08:05 132387 /usr/lib/libXt.so.6.0.0 b6e8b000-b6ea0000 r-xp 00000000 08:05 132373 /usr/lib/libXmu.so.6.2.0 b6ea0000-b6ea1000 rw-p 00015000 08:05 132373 /usr/lib/libXmu.so.6.2.0 b6ea1000-b6efe000 r-xp 00000000 08:05 131507 /usr/lib/libGL.so.1.2 b6efe000-b6f00000 rw-p 0005d000 08:05 131507 /usr/lib/libGL.so.1.2 b6f02000-b6f81000 r-xp 00000000 08:05 132036 /usr/lib/libGLU.so.1.3.060502 b6f81000-b6f82000 rw-p 0007e000 08:05 132036 /usr/lib/libGLU.so.1.3.060502 b6f82000-b6f83000 r--s 00000000 08:05 1344348 /var/cache/fontconfig/92a571655fb1c0ec1c4d6f496220600a-x86.cache-2 b6f83000-b6f84000 r--s 00000000 08:05 5390488 /home/kshtejer/local/JAIDA-3.2.3/lib/aida-dev.jar b6f84000-b6f88000 rw-s 00000000 08:05 7716995 /tmp/hsperfdata_kshtejer/32607 b6f88000-b6f8f000 r-xp 00000000 08:05 5588239 /lib/tls/i686/cmov/libnss_compat-2.5.so b6f8f000-b6f91000 rw-p 00006000 08:05 5588239 /lib/tls/i686/cmov/libnss_compat-2.5.so b6f91000-b6f99000 r-xp 00000000 08:05 937636 /usr/lib/j2se/1.4/jre/lib/i386/native_threads/libhpi.so b6f99000-b6f9a000 rw-p 00007000 08:05 937636 /usr/lib/j2se/1.4/jre/lib/i386/native_threads/libhpi.so b6f9b000-b6fc1000 r-xp 00000000 08:05 4837981 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4globman.so b6fc1000-b6fc2000 rw-p 00026000 08:05 4837981 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4globman.so b6fc2000-b6ffe000 r-xp 00000000 08:05 4837985 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4intercoms.so b6ffe000-b6fff000 rw-p 0003c000 08:05 4837985 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4intercoms.so b6fff000-b7048000 r-xp 00000000 08:05 4837987 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4graphics_reps.so b7048000-b704a000 rw-p 00048000 08:05 4837987 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4graphics_reps.so b704a000-b70b5000 r-xp 00000000 08:05 4837989 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4materials.so b70b5000-b70b6000 rw-p 0006b000 08:05 4837989 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4materials.so b70b7000-b70e4000 r-xp 00000000 08:05 4837991 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4geometrymng.so b70e4000-b70e5000 rw-p 0002d000 08:05 4837991 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4geometrymng.so b70e6000-b7125000 r-xp 00000000 08:05 4838011 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4partman.so b7125000-b715b000 rw-p 0003e000 08:05 4838011 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4partman.so b715c000-b7178000 r-xp 00000000 08:05 4837995 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4magneticfield.so b7178000-b7179000 rw-p 0001c000 08:05 4837995 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4magneticfield.so b7179000-b718a000 r-xp 00000000 08:05 4838027 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4track.so b718a000-b718b000 rw-p 00011000 08:05 4838027 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4track.so b718b000-b71a9000 r-xp 00000000 08:05 4837993 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4volumes.so b71a9000-b71aa000 rw-p 0001d000 08:05 4837993 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4volumes.so b71ac000-b71f9000 r-xp 00000000 08:05 4837997 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4navigation.so b71f9000-b71fa000 rw-p 0004c000 08:05 4837997 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4navigation.so b71fb000-b7227000 r-xp 00000000 08:05 4838037 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4procman.so b7227000-b7228000 rw-p 0002b000 08:05 4838037 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4procman.so b7229000-b7243000 r-xp 00000000 08:05 4838039 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4cuts.so b7243000-b7244000 rw-p 00019000 08:05 4838039 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4cuts.so b7244000-b7252000 r-xp 00000000 08:05 4837983 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hepnumerics.so b7252000-b7253000 rw-p 0000e000 08:05 4837983 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hepnumerics.so b7253000-b7257000 r-xp 00000000 08:05 4838013 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4bosons.so b7257000-b7258000 rw-p 00003000 08:05 4838013 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4bosons.so b7259000-b725d000 r-xp 00000000 08:05 4838031 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hits.so b725d000-b725e000 rw-p 00004000 08:05 4838031 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hits.so b725e000-b729d000 r-xp 00000000 08:05 4838003 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4csg.so b729d000-b729e000 rw-p 0003f000 08:05 4838003 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4csg.so b729e000-b72a7000 r-xp 00000000 08:05 4838015 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4leptons.so b72a7000-b72a8000 rw-p 00009000 08:05 4838015 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4leptons.so b72a8000-b72ac000 r-xp 00000000 08:05 4838033 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4digits.so b72ac000-b72ad000 rw-p 00004000 08:05 4838033 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4digits.so b72ad000-b72b1000 r-xp 00000000 08:05 4838023 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4ions.so b72b1000-b72b2000 rw-p 00003000 08:05 4838023 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4ions.so b72b3000-b72cb000 r-xp 00000000 08:05 4838021 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4baryons.so b72cb000-b72cc000 rw-p 00017000 08:05 4838021 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4baryons.so b72cc000-b7327000 r-xp 00000000 08:05 4838057 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4emutils.so b7327000-b7328000 rw-p 0005a000 08:05 4838057 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4emutils.so b7329000-b733f000 r-xp 00000000 08:05 4838029 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4detector.so b733f000-b7340000 rw-p 00016000 08:05 4838029 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4detector.so b7340000-b7371000 r-xp 00000000 08:05 4838151 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4tracking.so b7371000-b7372000 rw-p 00030000 08:05 4838151 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4tracking.so b7373000-b7381000 r-xp 00000000 08:05 4837999 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4geombias.so b7381000-b7382000 rw-p 0000e000 08:05 4837999 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4geombias.so b7383000-b73dc000 r-xp 00000000 08:05 4838153 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4event.so b73dc000-b73dd000 rw-p 00059000 08:05 4838153 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4event.so b73de000-b73f1000 r-xp 00000000 08:05 4838019 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4mesons.so b73f1000-b73f2000 rw-p 00013000 08:05 4838019 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4mesons.so b73f2000-b7483000 r-xp 00000000 08:05 4838005 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4specsolids.so b7483000-b7485000 rw-p 00091000 08:05 4838005 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4specsolids.so b7486000-b7531000 r-xp 00000000 08:05 4838173 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4modeling.so b7531000-b7534000 rw-p 000ab000 08:05 4838173 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4modeling.so b7535000-b7545000 r-xp 00000000 08:05 4838049 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4transportation.so b7545000-b7546000 rw-p 00010000 08:05 4838049 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4transportation.so b7547000-b757a000 r-xp 00000000 08:05 4838147 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_util.so b757a000-b757b000 rw-p 00032000 08:05 4838147 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_util.so b757c000-b758c000 r-xp 00000000 08:05 4838121 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4had_mod_man.so b758c000-b758d000 rw-p 0000f000 08:05 4838121 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4had_mod_man.so b758d000-b75bf000 r-xp 00000000 08:05 4838155 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4run.so b75bf000-b75c0000 rw-p 00031000 08:05 4838155 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4run.so b75c1000-b75dd000 r-xp 00000000 08:05 4838141 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4had_mod_util.so b75dd000-b75de000 rw-p 0001c000 08:05 4838141 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4had_mod_util.so b75de000-b7605000 r-xp 00000000 08:05 4838101 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_multifragmentation.so b7605000-b7606000 rw-p 00027000 08:05 4838101 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_multifragmentation.so b7607000-b7684000 r-xp 00000000 08:05 4838067 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_xsect.so b7684000-b768a000 rw-p 0007c000 08:05 4838067 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_xsect.so b768c000-b76a4000 r-xp 00000000 08:05 4838105 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_util.so b76a4000-b76a5000 rw-p 00018000 08:05 4838105 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_util.so b76a5000-b76ee000 r-xp 00000000 08:05 4838017 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4shortlived.so b76ee000-b76ef000 rw-p 00049000 08:05 4838017 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4shortlived.so b76ef000-b772b000 r-xp 00000000 08:05 4838119 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_LE.so b772b000-b772d000 rw-p 0003b000 08:05 4838119 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_LE.so b77a3000-b77a8000 r-xp 00000000 08:05 4838099 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_management.so b77a8000-b77a9000 rw-p 00004000 08:05 4838099 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_management.so b77aa000-b77b9000 r-xp 00000000 08:05 4838007 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4geomBoolean.so b77b9000-b77ba000 rw-p 0000f000 08:05 4838007 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4geomBoolean.so b77ba000-b7864000 r-xp 00000000 08:05 4838175 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4vis_management.so b7864000-b7866000 rw-p 000aa000 08:05 4838175 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4vis_management.so b7867000-b788e000 r-xp 00000000 08:05 4838091 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fermi_breakup.so b788e000-b788f000 rw-p 00027000 08:05 4838091 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fermi_breakup.so b7890000-b7930000 r-xp 00000000 08:05 4838109 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_HE.so b7930000-b7932000 rw-p 0009f000 08:05 4838109 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_HE.so b79ae000-b79bc000 r-xp 00000000 08:05 4838093 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fission.so b79bc000-b79bd000 rw-p 0000d000 08:05 4838093 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fission.so b79be000-b79d1000 r-xp 00000000 08:05 4838069 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_mgt.so b79d1000-b79d2000 rw-p 00012000 08:05 4838069 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_mgt.so b79d2000-b7abc000 r-xp 00000000 08:05 4838061 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4emlowenergy.so b7abc000-b7ac3000 rw-p 000e9000 08:05 4838061 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4emlowenergy.so b7ac6000-b7aef000 r-xp 00000000 08:05 4838103 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_photon_evaporation.so b7aef000-b7af0000 rw-p 00029000 08:05 4838103 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_photon_evaporation.so b7af1000-b7afb000 r-xp 00000000 08:05 4838143 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_proc.so b7afb000-b7afc000 rw-p 0000a000 08:05 4838143 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_proc.so b7afc000-b7c5f000 r-xp 00000000 08:05 4838095 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_gem_evaporation.so b7c5f000-b7c63000 rw-p 00162000 08:05 4838095 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_gem_evaporation.so b7c67000-b7c8b000 r-xp 00000000 08:05 4838089 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_evaporation.so b7c8b000-b7c8c000 rw-p 00024000 08:05 4838089 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_evaporation.so b7c8d000-b7c93000 r-xp 00000000 08:05 4838097 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_handler.so b7c93000-b7c94000 rw-p 00005000 08:05 4838097 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_handler.so b7c94000-b7cc4000 r-xp 00000000 08:05 4838145 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_stop.so b7cc4000-b7cc7000 rw-p 0002f000 08:05 4838145 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4hadronic_stop.so b7cc8000-b7cea000 r-xp 00000000 08:05 4838183 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4VRML.so b7cea000-b7cec000 rw-p 00021000 08:05 4838183 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4VRML.so b7cec000-b7d62000 r-xp 00000000 08:05 4838055 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4emstandard.so b7d62000-b7d65000 rw-p 00075000 08:05 4838055 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4emstandard.so b7d67000-b7d79000 r-xp 00000000 08:05 4838185 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4Tree.so b7d79000-b7d7a000 rw-p 00011000 08:05 4838185 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4Tree.so b7d7a000-b7d8c000 r-xp 00000000 08:05 4838167 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4UIcommon.so b7d8c000-b7d8d000 rw-p 00011000 08:05 4838167 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4UIcommon.so b7d8d000-b7da8000 r-xp 00000000 08:05 4838181 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4RayTracer.so b7da8000-b7daa000 rw-p 0001a000 08:05 4838181 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4RayTracer.so b7daa000-b7dc2000 r-xp 00000000 08:05 4838053 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4muons.so b7dc2000-b7dc4000 rw-p 00017000 08:05 4838053 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4muons.so b7dc4000-b7dcc000 r-xp 00000000 08:05 4838043 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4decay.so b7dcc000-b7dcd000 rw-p 00008000 08:05 4838043 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4decay.so b7dce000-b7dff000 r-xp 00000000 08:05 4838189 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4OpenGL.so b7dff000-b7e01000 rw-p 00030000 08:05 4838189 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4OpenGL.so b7e02000-b7e97000 r-xp 00000000 08:05 4838179 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4visHepRep.so b7e97000-b7e9b000 rw-p 00095000 08:05 4838179 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4visHepRep.so b7e9b000-b7eb3000 r-xp 00000000 08:05 4838177 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4FR.so b7eb3000-b7eb4000 rw-p 00018000 08:05 4838177 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4FR.so b7eb4000-b7ec8000 r-xp 00000000 08:05 4838169 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4UIbasic.so b7ec8000-b7ec9000 rw-p 00014000 08:05 4838169 /home/kshtejer/CERN/alice/geant4/lib/Linux-g++/libG4UIbasic.so b7ec9000-b7f2a000 r-xp 00000000 08:05 5391333 /home/kshtejer/CERN/work/g4work/tmp/Linux-g++/A01app/libA01app.so b7f2a000-b7f2d000 rw-p 00060000 08:05 5391333 /home/kshtejer/CERN/work/g4work/tmp/Linux-g++/A01app/libA01app.so b7f31000-b7f4a000 r-xp 00000000 08:05 5554197 /lib/ld-2.5.so b7f4a000-b7f4c000 rw-p 00019000 08:05 5554197 /lib/ld-2.5.so bf83d000-bf853000 rwxp bf83d000 00:00 0 [stack] ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] Heap at VM Abort: Heap def new generation total 576K, used 198K [0xaa360000, 0xaa400000, 0xaa840000) eden space 512K, 26% used [0xaa360000, 0xaa381988, 0xaa3e0000) from space 64K, 100% used [0xaa3e0000, 0xaa3f0000, 0xaa3f0000) to space 64K, 0% used [0xaa3f0000, 0xaa3f0000, 0xaa400000) tenured generation total 1408K, used 1380K [0xaa840000, 0xaa9a0000, 0xae360000) the space 1408K, 98% used [0xaa840000, 0xaa999120, 0xaa999200, 0xaa9a0000) compacting perm gen total 4096K, used 4089K [0xae360000, 0xae760000, 0xb2360000) the space 4096K, 99% used [0xae360000, 0xae75e4f0, 0xae75e600, 0xae760000) Local Time = Mon Oct 15 13:05:39 2007 Elapsed Time = 2 # # The exception above was detected in native code outside the VM # # Java VM: Java HotSpot(TM) Client VM (Blackdown-1.4.2-02 mixed mode) #

Re: Now A01 links but does not run by Mark Donszelmann <Mark Donszelmann>, 15 Oct, 2007
Re: Re:Now A01 links but does not run (Katherin Shtejer Diaz)

Hi from the trace I see you probably cannot open a Window over some XServer. Make sure you can run a simple xterm from the same command line and it can open a window. A01, when compiled with Analysis, will open a window with 4 histograms as an example. Regards Mark On Oct 15, 2007, at 1:30 PM, Katherin Shtejer Diaz wrote: > *** Discussion title: Analysis > Email replies to PublicHyperNews@slac.stanford.edu must include: > In-Reply-To: <"/analysis/277/1/1/1/1/1/1"@geant4- > hn.slac.stanford.edu> > Subject: ...change this to be about your reply. > > Hello again, > > Finally I have successfully built the AIDAJNI-3.2.3 from the source > and compiled the extended example A01, using JAIDA-3.2.3 and > AIDAJNI-3.2.3. > It compiled and linked OK!!! > > But the running process aborted with the following message: > > ********************************************** > > Local Time = Mon Oct 15 13:05:39 2007 > Elapsed Time = 2 > # > # The exception above was detected in native code outside the VM > # > # Java VM: Java HotSpot(TM) Client VM (Blackdown-1.4.2-02 mixed mode) > # > # An error report file has been saved as hs_err_pid32607.log. > # Please refer to the file for further information. > # > Aborted (core dumped) > > ********************************************** > > I am using Ubuntu. I would like to remark that I have done the same > installation > of Geant4.9.0 under Scientific Linux 4.5, in other computer and the > same > problem is happening related to jaida-aidajni (compiled from the > source) when running the example A01. > > Please, I would appreciate any idea to solve this problem. > > Here I am posting the log error report file. Maybe it could be > usefull. > > Than you in advance, > > Katherin > > The log file: > > An unexpected exception has been detected in native code outside > the VM. > Unexpected Signal : 11 occurred at PC=0xA98BE98A > Function=_XmGetFocusData+0x72 > Library=/usr/lib/j2se/1.4/jre/lib/i386/libXm.so.3 > > Current Java thread: > at sun.awt.motif.MWindowPeer.pCreate(Native Method) > at sun.awt.motif.MWindowPeer.create(MWindowPeer.java:79) > at sun.awt.motif.MComponentPeer.init(MComponentPeer.java:222) > at sun.awt.motif.MWindowPeer.init(MWindowPeer.java:90) > at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:58) > at sun.awt.motif.MToolkit.createFrame(MToolkit.java:209) > at java.awt.Frame.addNotify(Frame.java:472) > - locked <0xaa85d710> (a java.awt.Component$AWTTreeLock) > at java.awt.Window.pack(Window.java:436) > at hep.aida.ref.plotter.Plotter.show(Plotter.java:74) > > Dynamic libraries: > 08048000-0804d000 r-xp 00000000 08:05 4900458 /home/kshtejer/ > CERN/work/g4work/bin/Linux-g++/A01app > 0804d000-0804e000 rw-p 00004000 08:05 4900458 /home/kshtejer/ > CERN/work/g4work/bin/Linux-g++/A01app > 0804e000-0854a000 rw-p 0804e000 00:00 0 [heap] > a9590000-a9596000 r--s 00000000 08:05 1343580 /var/cache/ > fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-x86.cache-2 > a9596000-a9597000 r--s 00000000 08:05 1344044 /var/cache/ > fontconfig/fd9505950c048a77dc4b710eb6a628ed-x86.cache-2 > a9597000-a959a000 r--s 00000000 08:05 1344043 /var/cache/ > fontconfig/ddc79d3ea06a7c6ffa86ede85f3bb5df-x86.cache-2 > a959a000-a959b000 r--s 00000000 08:05 1344042 /var/cache/ > fontconfig/e7071f4a29fa870f4323321c154eba04-x86.cache-2 > a959b000-a959c000 r--s 00000000 08:05 1344041 /var/cache/ > fontconfig/a2ab74764b07279e7c36ddb1d302cf26-x86.cache-2 > a959c000-a95a0000 r--s 00000000 08:05 1343577 /var/cache/ > fontconfig/921a30a17f0be15c70ac14043cb7a739-x86.cache-2 > a95a0000-a95a1000 r--s 00000000 08:05 1344039 /var/cache/ > fontconfig/4c73fe0c47614734b17d736dbde7580a-x86.cache-2 > a95a1000-a95a3000 r--s 00000000 08:05 1344038 /var/cache/ > fontconfig/646addb8444faa74ee138aa00ab0b6a0-x86.cache-2 > a95a3000-a95a5000 r--s 00000000 08:05 1344037 /var/cache/ > fontconfig/20bd79ad97094406f7d1b9654bfbd926-x86.cache-2 > a95a5000-a95a6000 r--s 00000000 08:05 1344036 /var/cache/ > fontconfig/75a2cd575a62c63e802c11411fb87c37-x86.cache-2 > a95a6000-a95a8000 r--s 00000000 08:05 1344035 /var/cache/ > fontconfig/9c0624108b9a2ae8552f664125be8356-x86.cache-2 > a95a8000-a95ae000 r--s 00000000 08:05 1344034 /var/cache/ > fontconfig/6d41288fd70b0be22e8c3a91e032eec0-x86.cache-2 > a95ae000-a95b0000 r--s 00000000 08:05 1344033 /var/cache/ > fontconfig/de156ccd2eddbdc19d37a45b8b2aac9c-x86.cache-2 > a95b0000-a95b2000 r--s 00000000 08:05 1344032 /var/cache/ > fontconfig/da1bd5ca8443ffe22927a23ce431d198-x86.cache-2 > a95b2000-a95ba000 r--s 00000000 08:05 1344031 /var/cache/ > fontconfig/e3de0de479f42330eadf588a55fb5bf4-x86.cache-2 > a95ba000-a95c0000 r--s 00000000 08:05 1344030 /var/cache/ > fontconfig/0f34bcd4b6ee430af32735b75db7f02b-x86.cache-2 > a95c0000-a95c1000 r--s 00000000 08:05 1344054 /var/cache/ > fontconfig/9451a55048e8dbe8633e64d34165fdf2-x86.cache-2 > a95c1000-a95c2000 r--s 00000000 08:05 1344029 /var/cache/ > fontconfig/4794a0821666d79190d59a36cb4f44b5-x86.cache-2 > a95c2000-a95c4000 r--s 00000000 08:05 1344351 /var/cache/ > fontconfig/2c5ba8142dffc8bf0377700342b8ca1a-x86.cache-2 > a95c4000-a95c6000 r--s 00000000 08:05 1344028 /var/cache/ > fontconfig/de9486f0b47a4d768a594cb4198cb1c6-x86.cache-2 > a95c6000-a95cc000 r--s 00000000 08:05 1344027 /var/cache/ > fontconfig/d52a8644073d54c13679302ca1180695-x86.cache-2 > a95cc000-a95d0000 r--s 00000000 08:05 1344050 /var/cache/ > fontconfig/105b9c7e6f0a4f82d8c9b6e39c52c6f9-x86.cache-2 > a95d0000-a95d3000 r--s 00000000 08:05 1344026 /var/cache/ > fontconfig/6386b86020ecc1ef9690bb720a13964f-x86.cache-2 > a95d3000-a95d7000 r--s 00000000 08:05 1343562 /var/cache/ > fontconfig/089dead882dea3570ffc31a9898cfb69-x86.cache-2 > a95d7000-a95de000 r--s 00000000 08:05 1344789 /var/cache/ > fontconfig/e13b20fdb08344e0e664864cc2ede53d-x86.cache-2 > a95de000-a95df000 r--s 00000000 08:05 1344069 /var/cache/ > fontconfig/fcff1cd55d48a2c86a175e9943c3506d-x86.cache-2 > a95df000-a95e1000 r--s 00000000 08:05 1344741 /var/cache/ > fontconfig/e9e44584608a73233979f764b5f9dd81-x86.cache-2 > a95e1000-a95e2000 r--s 00000000 08:05 1344067 /var/cache/ > fontconfig/b5a4f3f568a71026ccdc6a3a51afa9b4-x86.cache-2 > a95e2000-a95e3000 r--s 00000000 08:05 1344739 /var/cache/ > fontconfig/e22b663d51a3e226824aa2afd6c591f7-x86.cache-2 > a95e3000-a95e4000 r--s 00000000 08:05 1344066 /var/cache/ > fontconfig/2561679576a9c7fd2ce41d281d4e00d1-x86.cache-2 > a95e4000-a95e5000 r--s 00000000 08:05 1344349 /var/cache/ > fontconfig/bf1f9632594a1fa28e2cf4d7888deffe-x86.cache-2 > a95e5000-a95e6000 r--s 00000000 08:05 1344065 /var/cache/ > fontconfig/b8613a33de00eecd32d5a94c3c617829-x86.cache-2 > a95e6000-a95e9000 r--s 00000000 08:05 1344064 /var/cache/ > fontconfig/b21a91cee725896328b8cee8091cf747-x86.cache-2 > a95e9000-a95ee000 r--s 00000000 08:05 1344063 /var/cache/ > fontconfig/fd9416c4b92f07c6f59a3a8cf496e9dc-x86.cache-2 > a95ee000-a95f0000 r--s 00000000 08:05 1344357 /var/cache/ > fontconfig/059138ec877db160474b4d5de1248d14-x86.cache-2 > a95f0000-a95f1000 r--s 00000000 08:05 1344061 /var/cache/ > fontconfig/f5a93ac943883aa0fd9a7bfe0f6ec3c1-x86.cache-2 > a95f1000-a95f3000 r--s 00000000 08:05 1344356 /var/cache/ > fontconfig/118d8d5311348bbdf5fe3b106d7c13d4-x86.cache-2 > a95f3000-a95f4000 r--s 00000000 08:05 1344059 /var/cache/ > fontconfig/a1131b7be650f9abae4907495aa5815d-x86.cache-2 > a95f4000-a95f9000 r--s 00000000 08:05 1344058 /var/cache/ > fontconfig/8ab5f685cd6d8ba67c37c908faf08172-x86.cache-2 > a95f9000-a95fd000 r--s 00000000 08:05 1344355 /var/cache/ > fontconfig/0f32d3adc6a232110812e17374eaa446-x86.cache-2 > a95fd000-a95ff000 r--s 00000000 08:05 1344056 /var/cache/ > fontconfig/7b4a97c10f6c0166998ddfa1cf7392fb-x86.cache-2 > a95ff000-a9602000 r--s 00000000 08:05 1344055 /var/cache/ > fontconfig/61c830dfac3fd78a12654da5e9ba3f56-x86.cache-2 > a9602000-a9603000 r--s 00000000 08:05 1344354 /var/cache/ > fontconfig/e0f9e95429e756d56293ed4d63866094-x86.cache-2 > a9603000-a9605000 r--s 00000000 08:05 1344053 /var/cache/ > fontconfig/4123634e9c08547d899d0aaff05ebe69-x86.cache-2 > a9605000-a9609000 r--s 00000000 08:05 1344052 /var/cache/ > fontconfig/142ecfc435bad6f1fbc2648c1119d5eb-x86.cache-2 > a9609000-a960f000 r--s 00000000 08:05 1344051 /var/cache/ > fontconfig/102e5142c2e9e50c5e8ece26694a2dad-x86.cache-2 > a96aa000-a96ae000 r-xp 00000000 08:05 132363 /usr/lib/ > libXfixes.so.3.1.0 > a96ae000-a96af000 rw-p 00003000 08:05 132363 /usr/lib/ > libXfixes.so.3.1.0 > a96af000-a96b6000 r-xp 00000000 08:05 132383 /usr/lib/ > libXrender.so.1.3.0 > a96b6000-a96b7000 rw-p 00006000 08:05 132383 /usr/lib/ > libXrender.so.1.3.0 > a96b7000-a96bf000 r-xp 00000000 08:05 132353 /usr/lib/ > libXcursor.so.1.0.2 > a96bf000-a96c0000 rw-p 00007000 08:05 132353 /usr/lib/ > libXcursor.so.1.0.2 > a96d9000-a9776000 r-xp 00000000 08:05 805035 /usr/lib/j2se/1.4/ > jre/lib/i386/libfontmanager.so > a9776000-a9788000 rw-p 0009d000 08:05 805035 /usr/lib/j2se/1.4/ > jre/lib/i386/libfontmanager.so > a978c000-a9790000 r-xp 00000000 08:05 132389 /usr/lib/ > libXtst.so.6.1.0 > a9790000-a9791000 rw-p 00003000 08:05 132389 /usr/lib/ > libXtst.so.6.1.0 > a9791000-a9798000 r-xp 00000000 08:05 132377 /usr/lib/libXp.so. > 6.2.0 > a9798000-a9799000 rw-p 00006000 08:05 132377 /usr/lib/libXp.so. > 6.2.0 > a9799000-a97a3000 r--s 00000000 08:05 1344352 /var/cache/ > fontconfig/a960c40fc9306f090224a04585f8a963-x86.cache-2 > a97a3000-a97a5000 r--s 00000000 08:05 1344048 /var/cache/ > fontconfig/9404ff413c67fc2a1526fd14eb4163a8-x86.cache-2 > a97a5000-a97a9000 r--s 00000000 08:05 1344350 /var/cache/ > fontconfig/b3fedf7c409f006ca1a6fceffceb77cf-x86.cache-2 > a97a9000-a97ab000 r--s 00000000 08:05 1343592 /var/cache/ > fontconfig/6330322105e0c4105d7c7a6ea2974107-x86.cache-2 > a97ab000-a97b2000 r--s 00000000 08:05 1344788 /var/cache/ > fontconfig/beeeeb3dfe132a8a0633a017c99ce0c0-x86.cache-2 > a97b2000-a99a4000 r-xp 00000000 08:05 805019 /usr/lib/j2se/1.4/ > jre/lib/i386/libXm.so.3 > a99a4000-a99be000 rw-p 001f1000 08:05 805019 /usr/lib/j2se/1.4/ > jre/lib/i386/libXm.so.3 > a99bf000-a9a25000 r-xp 00000000 08:05 805016 /usr/lib/j2se/1.4/ > jre/lib/i386/libmlib_image.so > a9a25000-a9a26000 rw-p 00066000 08:05 805016 /usr/lib/j2se/1.4/ > jre/lib/i386/libmlib_image.so > a9a26000-a9b07000 r-xp 00000000 08:05 805027 /usr/lib/j2se/1.4/ > jre/lib/i386/libawt.so > a9b07000-a9b10000 rw-p 000e0000 08:05 805027 /usr/lib/j2se/1.4/ > jre/lib/i386/libawt.so > a9b34000-a9b3c000 r--s 00000000 08:05 5390487 /home/kshtejer/ > local/JAIDA-3.2.3/lib/aida.jar > a9b3c000-a9bbb000 r--s 00000000 08:05 5390492 /home/kshtejer/ > local/JAIDA-3.2.3/lib/bcel.jar > a9bbb000-a9c6d000 r--s 00000000 08:05 5390490 /home/kshtejer/ > local/JAIDA-3.2.3/lib/freehep-base.jar > a9c6d000-a9d77000 r--s 00000000 08:05 5390489 /home/kshtejer/ > local/JAIDA-3.2.3/lib/freehep-hep.jar > a9d77000-a9e0e000 r--s 00000000 08:05 5390495 /home/kshtejer/ > local/JAIDA-3.2.3/lib/jas-plotter.jar > a9e0e000-a9e17000 r--s 00000000 08:05 5390493 /home/kshtejer/ > local/JAIDA-3.2.3/lib/jel.jar > a9e17000-a9e27000 r--s 00000000 08:05 5390491 /home/kshtejer/ > local/JAIDA-3.2.3/lib/openide-lookup.jar > a9e27000-a9e33000 r--s 00000000 08:05 5390494 /home/kshtejer/ > local/JAIDA-3.2.3/lib/optimizers.jar > a9e33000-a9e38000 r--s 00000000 08:05 5391259 /home/kshtejer/ > local/AIDAJNI-3.2.3/lib/freehep-aidajni.jar > a9e38000-a9e54000 r--s 00000000 08:05 937615 /usr/lib/j2se/1.4/ > jre/lib/ext/sunjce_provider.jar > a9e54000-a9f10000 r--s 00000000 08:05 937617 /usr/lib/j2se/1.4/ > jre/lib/ext/localedata.jar > a9f10000-a9f1e000 r--s 00000000 08:05 937616 /usr/lib/j2se/1.4/ > jre/lib/ext/ldapsec.jar > aa122000-aa15d000 r--p 00000000 08:05 197923 /usr/lib/locale/ > en_US.utf8/LC_CTYPE > b2361000-b2364000 r--s 00000000 08:05 937614 /usr/lib/j2se/1.4/ > jre/lib/ext/dnsns.jar > b440c000-b49ac000 r--s 00000000 08:05 512694 /usr/lib/j2se/1.4/ > jre/lib/charsets.jar > b49ac000-b49bd000 r--s 00000000 08:05 512692 /usr/lib/j2se/1.4/ > jre/lib/jce.jar > b49bd000-b4a9a000 r--s 00000000 08:05 512690 /usr/lib/j2se/1.4/ > jre/lib/jsse.jar > b4a9a000-b4ab0000 r--s 00000000 08:05 512696 /usr/lib/j2se/1.4/ > jre/lib/sunrsasign.jar > b4afa000-b64a6000 r--s 00000000 08:05 512697 /usr/lib/j2se/1.4/ > jre/lib/rt.jar > b64a6000-b64b7000 r-xp 00000000 08:05 805023 /usr/lib/j2se/1.4/ > jre/lib/i386/libzip.so > b64b7000-b64b9000 rw-p 00011000 08:05 805023 /usr/lib/j2se/1.4/ > jre/lib/i386/libzip.so > b64b9000-b64d8000 r-xp 00000000 08:05 805013 /usr/lib/j2se/1.4/ > jre/lib/i386/libjava.so > b64d8000-b64d9000 rw-p 0001f000 08:05 805013 /usr/lib/j2se/1.4/ > jre/lib/i386/libjava.so > b64d9000-b64e2000 r-xp 00000000 08:05 5588243 /lib/tls/i686/cmov/ > libnss_files-2.5.so > b64e2000-b64e4000 rw-p 00008000 08:05 5588243 /lib/tls/i686/cmov/ > libnss_files-2.5.so > b64e4000-b64ec000 r-xp 00000000 08:05 5588247 /lib/tls/i686/cmov/ > libnss_nis-2.5.so > b64ec000-b64ee000 rw-p 00007000 08:05 5588247 /lib/tls/i686/cmov/ > libnss_nis-2.5.so > b64ee000-b64f5000 r--s 00000000 08:05 4866283 /usr/lib/gconv/ > gconv-modules.cache > b64f5000-b6506000 r-xp 00000000 08:05 805015 /usr/lib/j2se/1.4/ > jre/lib/i386/libverify.so > b6506000-b6507000 rw-p 00011000 08:05 805015 /usr/lib/j2se/1.4/ > jre/lib/i386/libverify.so > b650c000-b651f000 r-xp 00000000 08:05 5588237 /lib/tls/i686/cmov/ > libnsl-2.5.so > b651f000-b6521000 rw-p 00012000 08:05 5588237 /lib/tls/i686/cmov/ > libnsl-2.5.so > b6523000-b6527000 r-xp 00000000 08:05 132357 /usr/lib/ > libXdmcp.so.6.0.0 > b6527000-b6528000 rw-p 00003000 08:05 132357 /usr/lib/ > libXdmcp.so.6.0.0 > b6528000-b652a000 r-xp 00000000 08:05 132346 /usr/lib/libXau.so. > 6.0.0 > b652a000-b652b000 rw-p 00001000 08:05 132346 /usr/lib/libXau.so. > 6.0.0 > b652b000-b6533000 r-xp 00000000 08:05 132506 /usr/lib/libdrm.so. > 2.3.0 > b6533000-b6534000 rw-p 00008000 08:05 132506 /usr/lib/libdrm.so. > 2.3.0 > b6534000-b6536000 r-xp 00000000 08:05 5588232 /lib/tls/i686/cmov/ > libdl-2.5.so > b6536000-b6538000 rw-p 00001000 08:05 5588232 /lib/tls/i686/cmov/ > libdl-2.5.so > b6539000-b654c000 r-xp 00000000 08:05 5588252 /lib/tls/i686/cmov/ > libpthread-2.5.so > b654c000-b654e000 rw-p 00013000 08:05 5588252 /lib/tls/i686/cmov/ > libpthread-2.5.so > b6550000-b6554000 r-xp 00000000 08:05 132397 /usr/lib/ > libXxf86vm.so.1.0.0 > b6554000-b6555000 rw-p 00003000 08:05 132397 /usr/lib/ > libXxf86vm.so.1.0.0 > b6556000-b6691000 r-xp 00000000 08:05 5588226 /lib/tls/i686/cmov/ > libc-2.5.so > b6691000-b6692000 r--p 0013b000 08:05 5588226 /lib/tls/i686/cmov/ > libc-2.5.so > b6692000-b6694000 rw-p 0013c000 08:05 5588226 /lib/tls/i686/cmov/ > libc-2.5.so > b6697000-b66a2000 r-xp 00000000 08:05 5554240 /lib/libgcc_s.so.1 > b66a2000-b66a3000 rw-p 0000a000 08:05 5554240 /lib/libgcc_s.so.1 > b66a3000-b66c8000 r-xp 00000000 08:05 5588234 /lib/tls/i686/cmov/ > libm-2.5.so > b66c8000-b66ca000 rw-p 00024000 08:05 5588234 /lib/tls/i686/cmov/ > libm-2.5.so > b66ca000-b67a9000 r-xp 00000000 08:05 133037 /usr/lib/libstdc+ > +.so.6.0.8 > b67a9000-b67ac000 r--p 000de000 08:05 133037 /usr/lib/libstdc+ > +.so.6.0.8 > b67ac000-b67ae000 rw-p 000e1000 08:05 133037 /usr/lib/libstdc+ > +.so.6.0.8 > b67b5000-b6a76000 r-xp 00000000 08:05 937633 /usr/lib/j2se/1.4/ > jre/lib/i386/client/libjvm.so > b6a76000-b6a91000 rw-p 002c0000 08:05 937633 /usr/lib/j2se/1.4/ > jre/lib/i386/client/libjvm.so > b6aa8000-b6aaa000 r-xp 00000000 08:05 5391258 /home/kshtejer/ > local/AIDAJNI-3.2.3/lib/Linux-g++/libFHJNI.so > b6aaa000-b6aab000 rw-p 00001000 08:05 5391258 /home/kshtejer/ > local/AIDAJNI-3.2.3/lib/Linux-g++/libFHJNI.so > b6aab000-b6bc2000 r-xp 00000000 08:05 5391254 /home/kshtejer/ > local/AIDAJNI-3.2.3/lib/Linux-g++/libAIDAJNI.so > b6bc2000-b6bcf000 rw-p 00116000 08:05 5391254 /home/kshtejer/ > local/AIDAJNI-3.2.3/lib/Linux-g++/libAIDAJNI.so > b6bcf000-b6d13000 r-xp 00000000 08:05 4620909 /home/kshtejer/ > CERN/alice/clhep/lib/libCLHEP-2.0.3.1.so > b6d13000-b6d17000 rw-p 00144000 08:05 4620909 /home/kshtejer/ > CERN/alice/clhep/lib/libCLHEP-2.0.3.1.so > b6d19000-b6d2e000 r-xp 00000000 08:05 132318 /usr/lib/libICE.so. > 6.3.0 > b6d2e000-b6d30000 rw-p 00014000 08:05 132318 /usr/lib/libICE.so. > 6.3.0 > b6d32000-b6d3a000 r-xp 00000000 08:05 132336 /usr/lib/libSM.so. > 6.0.0 > b6d3a000-b6d3b000 rw-p 00007000 08:05 132336 /usr/lib/libSM.so. > 6.0.0 > b6d3b000-b6e28000 r-xp 00000000 08:05 132340 /usr/lib/libX11.so. > 6.2.0 > b6e28000-b6e2c000 rw-p 000ed000 08:05 132340 /usr/lib/libX11.so. > 6.2.0 > b6e2c000-b6e39000 r-xp 00000000 08:05 132361 /usr/lib/ > libXext.so.6.4.0 > b6e39000-b6e3a000 rw-p 0000d000 08:05 132361 /usr/lib/ > libXext.so.6.4.0 > b6e3a000-b6e87000 r-xp 00000000 08:05 132387 /usr/lib/libXt.so. > 6.0.0 > b6e87000-b6e8b000 rw-p 0004c000 08:05 132387 /usr/lib/libXt.so. > 6.0.0 > b6e8b000-b6ea0000 r-xp 00000000 08:05 132373 /usr/lib/libXmu.so. > 6.2.0 > b6ea0000-b6ea1000 rw-p 00015000 08:05 132373 /usr/lib/libXmu.so. > 6.2.0 > b6ea1000-b6efe000 r-xp 00000000 08:05 131507 /usr/lib/libGL.so.1.2 > b6efe000-b6f00000 rw-p 0005d000 08:05 131507 /usr/lib/libGL.so.1.2 > b6f02000-b6f81000 r-xp 00000000 08:05 132036 /usr/lib/libGLU.so. > 1.3.060502 > b6f81000-b6f82000 rw-p 0007e000 08:05 132036 /usr/lib/libGLU.so. > 1.3.060502 > b6f82000-b6f83000 r--s 00000000 08:05 1344348 /var/cache/ > fontconfig/92a571655fb1c0ec1c4d6f496220600a-x86.cache-2 > b6f83000-b6f84000 r--s 00000000 08:05 5390488 /home/kshtejer/ > local/JAIDA-3.2.3/lib/aida-dev.jar > b6f84000-b6f88000 rw-s 00000000 08:05 7716995 /tmp/ > hsperfdata_kshtejer/32607 > b6f88000-b6f8f000 r-xp 00000000 08:05 5588239 /lib/tls/i686/cmov/ > libnss_compat-2.5.so > b6f8f000-b6f91000 rw-p 00006000 08:05 5588239 /lib/tls/i686/cmov/ > libnss_compat-2.5.so > b6f91000-b6f99000 r-xp 00000000 08:05 937636 /usr/lib/j2se/1.4/ > jre/lib/i386/native_threads/libhpi.so > b6f99000-b6f9a000 rw-p 00007000 08:05 937636 /usr/lib/j2se/1.4/ > jre/lib/i386/native_threads/libhpi.so > b6f9b000-b6fc1000 r-xp 00000000 08:05 4837981 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4globman.so > b6fc1000-b6fc2000 rw-p 00026000 08:05 4837981 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4globman.so > b6fc2000-b6ffe000 r-xp 00000000 08:05 4837985 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4intercoms.so > b6ffe000-b6fff000 rw-p 0003c000 08:05 4837985 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4intercoms.so > b6fff000-b7048000 r-xp 00000000 08:05 4837987 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4graphics_reps.so > b7048000-b704a000 rw-p 00048000 08:05 4837987 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4graphics_reps.so > b704a000-b70b5000 r-xp 00000000 08:05 4837989 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4materials.so > b70b5000-b70b6000 rw-p 0006b000 08:05 4837989 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4materials.so > b70b7000-b70e4000 r-xp 00000000 08:05 4837991 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4geometrymng.so > b70e4000-b70e5000 rw-p 0002d000 08:05 4837991 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4geometrymng.so > b70e6000-b7125000 r-xp 00000000 08:05 4838011 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4partman.so > b7125000-b715b000 rw-p 0003e000 08:05 4838011 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4partman.so > b715c000-b7178000 r-xp 00000000 08:05 4837995 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4magneticfield.so > b7178000-b7179000 rw-p 0001c000 08:05 4837995 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4magneticfield.so > b7179000-b718a000 r-xp 00000000 08:05 4838027 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4track.so > b718a000-b718b000 rw-p 00011000 08:05 4838027 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4track.so > b718b000-b71a9000 r-xp 00000000 08:05 4837993 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4volumes.so > b71a9000-b71aa000 rw-p 0001d000 08:05 4837993 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4volumes.so > b71ac000-b71f9000 r-xp 00000000 08:05 4837997 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4navigation.so > b71f9000-b71fa000 rw-p 0004c000 08:05 4837997 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4navigation.so > b71fb000-b7227000 r-xp 00000000 08:05 4838037 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4procman.so > b7227000-b7228000 rw-p 0002b000 08:05 4838037 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4procman.so > b7229000-b7243000 r-xp 00000000 08:05 4838039 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4cuts.so > b7243000-b7244000 rw-p 00019000 08:05 4838039 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4cuts.so > b7244000-b7252000 r-xp 00000000 08:05 4837983 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hepnumerics.so > b7252000-b7253000 rw-p 0000e000 08:05 4837983 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hepnumerics.so > b7253000-b7257000 r-xp 00000000 08:05 4838013 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4bosons.so > b7257000-b7258000 rw-p 00003000 08:05 4838013 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4bosons.so > b7259000-b725d000 r-xp 00000000 08:05 4838031 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hits.so > b725d000-b725e000 rw-p 00004000 08:05 4838031 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hits.so > b725e000-b729d000 r-xp 00000000 08:05 4838003 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4csg.so > b729d000-b729e000 rw-p 0003f000 08:05 4838003 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4csg.so > b729e000-b72a7000 r-xp 00000000 08:05 4838015 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4leptons.so > b72a7000-b72a8000 rw-p 00009000 08:05 4838015 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4leptons.so > b72a8000-b72ac000 r-xp 00000000 08:05 4838033 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4digits.so > b72ac000-b72ad000 rw-p 00004000 08:05 4838033 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4digits.so > b72ad000-b72b1000 r-xp 00000000 08:05 4838023 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4ions.so > b72b1000-b72b2000 rw-p 00003000 08:05 4838023 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4ions.so > b72b3000-b72cb000 r-xp 00000000 08:05 4838021 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4baryons.so > b72cb000-b72cc000 rw-p 00017000 08:05 4838021 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4baryons.so > b72cc000-b7327000 r-xp 00000000 08:05 4838057 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4emutils.so > b7327000-b7328000 rw-p 0005a000 08:05 4838057 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4emutils.so > b7329000-b733f000 r-xp 00000000 08:05 4838029 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4detector.so > b733f000-b7340000 rw-p 00016000 08:05 4838029 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4detector.so > b7340000-b7371000 r-xp 00000000 08:05 4838151 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4tracking.so > b7371000-b7372000 rw-p 00030000 08:05 4838151 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4tracking.so > b7373000-b7381000 r-xp 00000000 08:05 4837999 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4geombias.so > b7381000-b7382000 rw-p 0000e000 08:05 4837999 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4geombias.so > b7383000-b73dc000 r-xp 00000000 08:05 4838153 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4event.so > b73dc000-b73dd000 rw-p 00059000 08:05 4838153 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4event.so > b73de000-b73f1000 r-xp 00000000 08:05 4838019 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4mesons.so > b73f1000-b73f2000 rw-p 00013000 08:05 4838019 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4mesons.so > b73f2000-b7483000 r-xp 00000000 08:05 4838005 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4specsolids.so > b7483000-b7485000 rw-p 00091000 08:05 4838005 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4specsolids.so > b7486000-b7531000 r-xp 00000000 08:05 4838173 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4modeling.so > b7531000-b7534000 rw-p 000ab000 08:05 4838173 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4modeling.so > b7535000-b7545000 r-xp 00000000 08:05 4838049 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4transportation.so > b7545000-b7546000 rw-p 00010000 08:05 4838049 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4transportation.so > b7547000-b757a000 r-xp 00000000 08:05 4838147 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_util.so > b757a000-b757b000 rw-p 00032000 08:05 4838147 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_util.so > b757c000-b758c000 r-xp 00000000 08:05 4838121 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4had_mod_man.so > b758c000-b758d000 rw-p 0000f000 08:05 4838121 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4had_mod_man.so > b758d000-b75bf000 r-xp 00000000 08:05 4838155 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4run.so > b75bf000-b75c0000 rw-p 00031000 08:05 4838155 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4run.so > b75c1000-b75dd000 r-xp 00000000 08:05 4838141 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4had_mod_util.so > b75dd000-b75de000 rw-p 0001c000 08:05 4838141 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4had_mod_util.so > b75de000-b7605000 r-xp 00000000 08:05 4838101 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/ > libG4hadronic_deex_multifragmentation.so > b7605000-b7606000 rw-p 00027000 08:05 4838101 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/ > libG4hadronic_deex_multifragmentation.so > b7607000-b7684000 r-xp 00000000 08:05 4838067 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_xsect.so > b7684000-b768a000 rw-p 0007c000 08:05 4838067 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_xsect.so > b768c000-b76a4000 r-xp 00000000 08:05 4838105 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_util.so > b76a4000-b76a5000 rw-p 00018000 08:05 4838105 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_util.so > b76a5000-b76ee000 r-xp 00000000 08:05 4838017 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4shortlived.so > b76ee000-b76ef000 rw-p 00049000 08:05 4838017 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4shortlived.so > b76ef000-b772b000 r-xp 00000000 08:05 4838119 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_LE.so > b772b000-b772d000 rw-p 0003b000 08:05 4838119 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_LE.so > b77a3000-b77a8000 r-xp 00000000 08:05 4838099 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_management.so > b77a8000-b77a9000 rw-p 00004000 08:05 4838099 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_management.so > b77aa000-b77b9000 r-xp 00000000 08:05 4838007 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4geomBoolean.so > b77b9000-b77ba000 rw-p 0000f000 08:05 4838007 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4geomBoolean.so > b77ba000-b7864000 r-xp 00000000 08:05 4838175 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4vis_management.so > b7864000-b7866000 rw-p 000aa000 08:05 4838175 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4vis_management.so > b7867000-b788e000 r-xp 00000000 08:05 4838091 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fermi_breakup.so > b788e000-b788f000 rw-p 00027000 08:05 4838091 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fermi_breakup.so > b7890000-b7930000 r-xp 00000000 08:05 4838109 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_HE.so > b7930000-b7932000 rw-p 0009f000 08:05 4838109 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_HE.so > b79ae000-b79bc000 r-xp 00000000 08:05 4838093 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fission.so > b79bc000-b79bd000 rw-p 0000d000 08:05 4838093 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_fission.so > b79be000-b79d1000 r-xp 00000000 08:05 4838069 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_mgt.so > b79d1000-b79d2000 rw-p 00012000 08:05 4838069 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_mgt.so > b79d2000-b7abc000 r-xp 00000000 08:05 4838061 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4emlowenergy.so > b7abc000-b7ac3000 rw-p 000e9000 08:05 4838061 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4emlowenergy.so > b7ac6000-b7aef000 r-xp 00000000 08:05 4838103 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/ > libG4hadronic_deex_photon_evaporation.so > b7aef000-b7af0000 rw-p 00029000 08:05 4838103 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/ > libG4hadronic_deex_photon_evaporation.so > b7af1000-b7afb000 r-xp 00000000 08:05 4838143 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_proc.so > b7afb000-b7afc000 rw-p 0000a000 08:05 4838143 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_proc.so > b7afc000-b7c5f000 r-xp 00000000 08:05 4838095 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_gem_evaporation.so > b7c5f000-b7c63000 rw-p 00162000 08:05 4838095 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_gem_evaporation.so > b7c67000-b7c8b000 r-xp 00000000 08:05 4838089 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_evaporation.so > b7c8b000-b7c8c000 rw-p 00024000 08:05 4838089 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_evaporation.so > b7c8d000-b7c93000 r-xp 00000000 08:05 4838097 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_handler.so > b7c93000-b7c94000 rw-p 00005000 08:05 4838097 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_deex_handler.so > b7c94000-b7cc4000 r-xp 00000000 08:05 4838145 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_stop.so > b7cc4000-b7cc7000 rw-p 0002f000 08:05 4838145 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4hadronic_stop.so > b7cc8000-b7cea000 r-xp 00000000 08:05 4838183 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4VRML.so > b7cea000-b7cec000 rw-p 00021000 08:05 4838183 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4VRML.so > b7cec000-b7d62000 r-xp 00000000 08:05 4838055 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4emstandard.so > b7d62000-b7d65000 rw-p 00075000 08:05 4838055 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4emstandard.so > b7d67000-b7d79000 r-xp 00000000 08:05 4838185 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4Tree.so > b7d79000-b7d7a000 rw-p 00011000 08:05 4838185 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4Tree.so > b7d7a000-b7d8c000 r-xp 00000000 08:05 4838167 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4UIcommon.so > b7d8c000-b7d8d000 rw-p 00011000 08:05 4838167 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4UIcommon.so > b7d8d000-b7da8000 r-xp 00000000 08:05 4838181 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4RayTracer.so > b7da8000-b7daa000 rw-p 0001a000 08:05 4838181 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4RayTracer.so > b7daa000-b7dc2000 r-xp 00000000 08:05 4838053 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4muons.so > b7dc2000-b7dc4000 rw-p 00017000 08:05 4838053 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4muons.so > b7dc4000-b7dcc000 r-xp 00000000 08:05 4838043 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4decay.so > b7dcc000-b7dcd000 rw-p 00008000 08:05 4838043 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4decay.so > b7dce000-b7dff000 r-xp 00000000 08:05 4838189 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4OpenGL.so > b7dff000-b7e01000 rw-p 00030000 08:05 4838189 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4OpenGL.so > b7e02000-b7e97000 r-xp 00000000 08:05 4838179 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4visHepRep.so > b7e97000-b7e9b000 rw-p 00095000 08:05 4838179 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4visHepRep.so > b7e9b000-b7eb3000 r-xp 00000000 08:05 4838177 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4FR.so > b7eb3000-b7eb4000 rw-p 00018000 08:05 4838177 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4FR.so > b7eb4000-b7ec8000 r-xp 00000000 08:05 4838169 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4UIbasic.so > b7ec8000-b7ec9000 rw-p 00014000 08:05 4838169 /home/kshtejer/ > CERN/alice/geant4/lib/Linux-g++/libG4UIbasic.so > b7ec9000-b7f2a000 r-xp 00000000 08:05 5391333 /home/kshtejer/ > CERN/work/g4work/tmp/Linux-g++/A01app/libA01app.so > b7f2a000-b7f2d000 rw-p 00060000 08:05 5391333 /home/kshtejer/ > CERN/work/g4work/tmp/Linux-g++/A01app/libA01app.so > b7f31000-b7f4a000 r-xp 00000000 08:05 5554197 /lib/ld-2.5.so > b7f4a000-b7f4c000 rw-p 00019000 08:05 5554197 /lib/ld-2.5.so > bf83d000-bf853000 rwxp bf83d000 00:00 0 [stack] > ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] > > Heap at VM Abort: > Heap > def new generation total 576K, used 198K [0xaa360000, > 0xaa400000, 0xaa840000) > eden space 512K, 26% used [0xaa360000, 0xaa381988, 0xaa3e0000) > from space 64K, 100% used [0xaa3e0000, 0xaa3f0000, 0xaa3f0000) > to space 64K, 0% used [0xaa3f0000, 0xaa3f0000, 0xaa400000) > tenured generation total 1408K, used 1380K [0xaa840000, > 0xaa9a0000, 0xae360000) > the space 1408K, 98% used [0xaa840000, 0xaa999120, 0xaa999200, > 0xaa9a0000) > compacting perm gen total 4096K, used 4089K [0xae360000, > 0xae760000, 0xb2360000) > the space 4096K, 99% used [0xae360000, 0xae75e4f0, 0xae75e600, > 0xae760000) > > Local Time = Mon Oct 15 13:05:39 2007 > Elapsed Time = 2 > # > # The exception above was detected in native code outside the VM > # > # Java VM: Java HotSpot(TM) Client VM (Blackdown-1.4.2-02 mixed mode) > # >

Re: Now A01 links but does not run by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 15 Oct, 2007 Re: Re: Now A01 links but does not run (Mark Donszelmann) Hi Mark, Thanks for your prompt answer. I tested what you recommended. The result is that with the command "xterm" from a simple command line a windows is opened. Anyway I am going to try with other examples that should generate aida output files to test if the error is the same. I will post the result here.. Thanks Katherin

Re: Now A01 links but does not run by Da <Da>, 16 Oct, 2007 Re: Re: Now A01 links but does not run (Katherin Shtejer Diaz) May be your aidaijni is not proper You should compile aidani(scr) to get aidajni

Re: Now A01 links but does not run by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 16 Oct, 2007 Re: Re: Now A01 links but does not run (Da) Hi, I just compiled AIDAJNI-3.2.3-src.tar.gz in my system, to get the AIDAJNI-3.2.3-Linux-g++.tar.gz. Regards Katherin

Both A01 and Hadr01, link but run is aborted by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 25 Oct, 2007 Re: Re: Now A01 links but does not run (Katherin Shtejer Diaz) Hello again, With extended/hadronic/Hadr01 the run seems to go OK when no parameters about the output format files are given. In this case the example runs apparentely OK but no histogram file is found at the end, in the spite of being reported the following: -------------------- ### Run 0 start ### Histo books 22 histograms Histo: tree store : histo.hbook WARNING: Scene "refresh" not found. /vis/scene/list to see scenes. EventAction: Event # 0 started RunAction: End of run actions are started ERROR: G4VisCommandsViewerUpdate::SetNewValue: no current viewer. HistoManager: End of run actions are started ======================================================== Beam particle geantino Beam Energy(MeV) 1000 Number of events 10 Average energy deposit (MeV) 0 RMS(MeV) 0 Average number of steps 300 Average number of gamma 0 Average number of e- 0 Average number of e+ 0 Average number of neutrons 0 Average number of protons 0 Average number of antiprotons 0 Average number of pi+ & pi- 0 Average number of pi0 0 Average number of kaons 0 Average number of muons 0 Average number of deuterons+tritons 0 Average number of He3+alpha 0 Average number of ions 0 Average number of forward neutrons 0 Average number of reflected neutrons 0 Average number of leaked neutrons 0 Average number of proton leak 0 Average number of pion leak 0 ======================================================== Closing the tree... Histograms and Ntuples are saved ------------------ If I change these parameters (i.e. /testhadr/HistoType) to choose aida, root or even hbook, then the run is abortes similarly to the "A01" example as follows: ----------------------------- Local Time = Thu Oct 25 21:25:53 2007 Elapsed Time = 78 # # The exception above was detected in native code outside the VM # # Java VM: Java HotSpot(TM) Client VM (Blackdown-1.4.2-02 mixed mode) # # An error report file has been saved as hs_err_pid13099.log. # Please refer to the file for further information. # Aborted (core dumped) --------------------- Please, It is being impossible to study the examples which produce histograms. I have already compiled the AIDAJNI from the source in the same system as the geant was compiled. I do not know what else can I do. Could some body help me with any idea, trick, hint...? I would appreciate very much! Best Regards, Katherin

Re: Both A01 and Hadr01, link but run is aborted by Katherin Shtejer Diaz <Katherin Shtejer Diaz>, 09 Nov, 2007 Re: Both A01 and Hadr01, link but run is aborted (Katherin Shtejer Diaz) Hello, Now I could solve the problem!!! The A01 and Hadr01 extended examples successfully compile and run giving rise to the corresponding histogram files. As I have chosen Ubuntu to work, the only trick that worked for me was re-install the Ubuntu with the main libraries, but not to install any of the additional Sun Java(TM) packages available with this linux. I only installed the j2sdk-1_5_0-linux.i586.bin from http://geant4.slac.stanford.edu/g4cd/August2005/AdditionalSoftware/Java/Linux/ and I have installed jaida and aidajni (3.2.1). The aidajni package was installed from the source and re-built in my OS-COMPILER system as described by Mark Donszelmann. By this way, I don´t get conflict between C++ and Java (JAIDA) Thanks very much for all advices, It were very useful to understand the problem. All the best, Katherin

Proble with OpenScientist v16r0 Keywords: OpenScientist by Nicolas Chouin <nicolas.chouin@univ-nantes.fr>, 25 Apr, 2007 Hello, I have changed my computer lately and have had to recompile Geant4.8.2 p01. I chose to install the new version of OpenScientist (v16.0) instead of v15.0 I used to use. Compilation is OK. But after I ran my first simulations I could not open the aida files with Jas3 and with programms I used to translate AIDA format into Excel format. Has anything changed in the format of AIDA files produced with OpenScientist (v16.0)? Thank you for your help. Nicolas Chouin. INSERM U601 Nantes, France.

Re: Proble with OpenScientist v16r0 Keywords: OpenScientist by Guy Barrand <Guy Barrand>, 26 Apr, 2007 Re: Proble with OpenScientist v16r0 (Nicolas Chouin) Hello Then, after an "offline" session, the problem comes from the fact that in OSC-15 I had put the logic, that if someone asks for the "hbook" format and that the HBOOK/ZEBRA driver of OSC was not here, then I produced an AIDA XML file format (obviously by issuing some warnings). But it appeared at usage (with other users here at LAL) that this in fact was awfully misleading since files are produced in batch and that the warnings finished to be not noticed in the flow of G4 outputs. And then people expect a .hbook and finish to have a .aida ! (And no way to trace things in the program, since a valid AIDA::ITree was anyway created). And then I have removed this logic in OSC-16. Now if someone ask for a given storage type and that the installed version has not the driver, then no file is produced. (Obviously some warnings are issued and the factory returns 0 at creation of the AIDA::ITree and then the user program can detect that something is wrong). Then in your case, in the code, it was requestd "hbook", but your OSC-15 produced a .aida that you were able to open with jas3. But since the osc_batch 16 kits have all the hbook drivers, now you have a true .hbook file. And it seems that your jas3 does not understand them. (Huum, I though that jas3 was able to open a .hbook file, but you have perhaps not some hbook reader plugin : you have to see with jas people here). Then, a way out, if wanting to use jas3 is to explicitly ask for "aida" or "xml" file production in your job. (Or arrange that your jas3 be able to read .hbook file). (You can learn PAW too...) (or try to use OSC/opaw). Guy

Re: Proble with OpenScientist v16r0 Keywords: OpenScientist by Nicolas Chouin <nicolas.chouin@univ-nantes.fr>, 26 Apr, 2007 Re: Re: Proble with OpenScientist v16r0 (Guy Barrand) Thank you, I explicitly ask for a XML file and now everything works fine... Moreover, I know better what I am doing :-) Nicolas Chouin

problems with getting histograms using JAIDA-3.2.4+AIDAJNI-3.2.3 Keywords: AIDA histograms by Victor_Makarov <Victor_Makarov>, 25 Apr, 2007 I've examined the forum and found out that many people have encountered a problem of histogram files absence. But I've found no clear solution. Make histclean won't help. My situation is that I get a histogram using analysis A01 example. It's ok - I've got an output. But working with lots of Testem's I have nothing, though I've got message that the information has been written in a corresponding file. Please help!

Re: problems with getting histograms using JAIDA-3.2.4+AIDAJNI-3.2.3 Keywords: AIDA histograms by Konstantinos Michael <Konstantinos Michael >, 11 May, 2007 Re: problems with getting histograms using JAIDA-3.2.4+AIDAJNI-3.2.3 (Victor_Makarov) i have exactly the same problem. for the A01 example jaida works fine but for the TestEm it doesent work!