Hi,
>Not sure from where to start debugging.
Use -gdb in your runjob and run again. You will get this message:
Attach gdb with the following command and 'c' from the gdb prompt:
  gdb - <PID>

Now open another terminal and run "gdb - <PID>". Type 'c' in gdb console and 
you 
will see the runjob on the other terminal is continuing. In the case of any 
SIGSEGV, gdb will return to its console. You can now run "backtrace" to see the 
call stack.
 
Hope that helps.
// Naderan *Mahmood;




________________________________
From: hardik soni <[email protected]>
To: [email protected]
Cc: chandran.raams <[email protected]>
Sent: Tue, December 28, 2010 10:37:27 PM
Subject: trouble in creating flexpoint

hi,

We have followed flexus-getting-started 4.0.0.pdf.
We currently facing problem in generating flexpoint.
Below is the output of runjob command with appropriate paths and variables. We 
are using flexus_test_app_x86.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

$./run_job -postprocess 
"/scratch/raam/flexus-4.0/scripts/postprocess_ckptgen.sh 
flexpoint 24 test_app" -cfg trace -run flexpoint -local -ckpt-gen 
CMP.MT4.L2Shared.Trace flexus_test_app_x86
Setting up flexus_test_app_x86 (0:0):  000:000
>/scratch/raam/flexus_dir/results/trace-CMP.MT4.L2Shared.Trace-29Dec10-002628/flexus_test_app_x86/000_000
>
Checking out a license... done: academic license.
Use of this software is subject to appropriate license.
Type 'copyright' for details on copyright.
Type 'help help' for info on the on-line documentation.

Image memory limited to 1 GB
Opening debug output file: debug.out
Opening debug output file: stats.out
Opening debug output file: trace.out
Successfully parsed debug configurations from debug.cfg
Initializing Flexus::ConfigurationManager...done
Initializing Flexus::ComponentManager...done
Entered init_local

Flexus (C) 2006-2010 The SimFlex Project
Eric Chung, Michael Ferdman, Brian Gold, Nikos Hardavellas, Jangwook Kim,
Ippokratis Pandis, Minglong Shao, Jared Smolens, Stephen Somogyi,
Evangelos Vlachos, Thomas Wenisch, Roland Wunderlich
Anastassia Ailamaki, Babak Falsafi and James C. Hoe.

Flexus Simics simulator - Built as CMP.MT4.L2Shared.Trace v1.0

1 <startup.cpp:121> {0}- Initializing Flexus.
2 <ComponentManager.cpp:80> {0}- Instantiating system with a width factor of: 4
3 <DecoupledFeeder.hpp:66> {0}- feeder port ToNAW is not wired
4 <SimicsTracer.cpp:617> {0}- Initializing SimicsTracerManager.
5 <SimicsTracer.cpp:730> {0}- Connecting: cpu0
6 <SimicsTracer.cpp:733> {0}- DecoupledFeeder connects Flexus cpu0 to Simics 
object cpu0
Segmentation fault (SIGSEGV) in main thread
The simulation state has been corrupted. Simulation cannot continue.
Please restart Simics.
Starting command line. (May have skipped commands in script files.)
simics> 

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------



Not sure from where to start debugging.
Has anyone face this problem before?
What do you think could be a problem?
I would appreciate your help.

-- 
Thanks & Regards,
Hardik Soni



      

Reply via email to