- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm running the newest VTune (as of last Tuesday, 2/12/2008) on Ubuntu 7.10 64-bit on a "Intel Core2 CPU 6600 @ 2.40GHz".
I'm trying to use VTune to profile a GNU Radio application. These applications are typically driven by Python scripts which use SWIG to interface with C++ libraries.
I set up the callgraph with the executable /usr/bin/python and the optional command-line arguments to be the python script. Console output looks like this:
Thanks,
Dan
I'm running the newest VTune (as of last Tuesday, 2/12/2008) on Ubuntu 7.10 64-bit on a "Intel Core2 CPU 6600 @ 2.40GHz".
I'm trying to use VTune to profile a GNU Radio application. These applications are typically driven by Python scripts which use SWIG to interface with C++ libraries.
I set up the callgraph with the executable /usr/bin/python and the optional command-line arguments to be the python script. Console output looks like this:
Thu Feb 21 13:19:55 2008 Reading property files started...
Thu Feb 21 13:19:55 2008 Reading property files done.
Thu Feb 21 13:19:55 2008 Static instrumentation started
Thu Feb 21 13:19:55 2008 Minimal instrumentation of module "python2.5" was skipped.
Thu Feb 21 13:19:55 2008 Exports instrumentation of module "libc-2.6.1.so" was skipped.
Thu Feb 21 13:19:55 2008 Minimal instrumentation of module "libdl-2.6.1.so" was skipped.
Thu Feb 21 13:19:55 2008 Exports instrumentation of module "libm-2.6.1.so" was skipped.
Thu Feb 21 13:19:55 2008 Exports instrumentation of module "libpthread-2.6.1.so" was skipped.
Thu Feb 21 13:19:55 2008 Exports instrumentation of module "libutil-2.6.1.so" was skipped.
Thu Feb 21 13:19:55 2008 Static instrumentation done
Thu Feb 21 13:19:55 2008 Warning for module "/usr/bin/python" - The module is stripped (Instrumentation degraded to MINIMAL).
Thu Feb 21 13:19:55 2008 Data collection started...
Thu Feb 21 13:19:55 2008 Static instrumentation started
Thu Feb 21 13:19:56 2008 All functions instrumentation of module "_gnuradio_swig_py_runtime.so" was successful.
Thu Feb 21 13:19:56 2008 Exports instrumentation of module "libfftw3f.so.3.1.2" was successful.
Thu Feb 21 13:19:56 2008 Exports instrumentation of module "libgcc_s.so.1" was successful.
Thu Feb 21 13:19:57 2008 All functions instrumentation of module "libgnuradio-core.so.0.0.0" was successful.
Thu Feb 21 13:19:57 2008 All functions instrumentation of module "libgromnithread.so.0.0.0" was successful.
Thu Feb 21 13:19:57 2008 Exports instrumentation of module "librt-2.6.1.so" was successful.
Thu Feb 21 13:19:58 2008 Exports instrumentation of module "libstdc++.so.6.0.9" was successful.
Thu Feb 21 13:19:58 2008 Static instrumentation done
Thu Feb 21 13:19:58 2008 Static instrumentation started
In the window in which I started vtlec, I see a bunch of "segmentation fault (core dumped)" lines of output, which makes me think whatever program is doing the static instrumentation is segfaulting.
At the end of this process, the window pops up with the output: "No results were generated for this run. Check the log or output window for further information".
If I try with a python command that just exits (e.g., I pass as the commandline argument a nonexist python source file), the call graph wizard works and gives me results. Any suggestions?Thanks,
Dan
Link Copied
0 Replies

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page