- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm currently evaluating VTune for use in profiling my MontaVista Carrier Grade Linux 3.1 application. I have followed the steps for building the remote data collector from app. note 30502201 and in general, VTune has performed well.
Unfortunately I am experiencing a problem when attempting to 'drill down' on one of the modules on the system - namely libc-2.3.2.so from the MontaVista glibc-2.3.2-25.0.27.0500612 rpm.
vtserver exits with a segmentation fault - stack trace as follows:
(gdb) where
#0 0x4069aec6 in CDWARF32Loader::define_files ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#1 0x4069a75b in CDWARF32Loader::Init_Comp_Unit_Prologue ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#2 0x40699fa7 in CDWARF32Loader::InitSrcIter ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#3 0x406998d9 in CDWARF32Loader::GetSrcFileIterator ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#4 0x402e6526 in CFileSymbolBankImpl::LoadLineInfo ()
from /opt/intel/vtune/rdc/shared/bin/libismImpl_2.so
#5 0x4030d9f3 in CFileSymbolBankImpl::CreateISMFile ()
from /opt/intel/vtune/rdc/shared/bin/libismImpl_2.so
#6 0x402c47ff in CAppSymbolBankImpl::AddFileSVEx ()
from /opt/intel/vtune/rdc/shared/bin/libismImpl_2.so
#7 0x402291c0 in GetDotISMLocal ()
from /opt/intel/vtune/rdc/shared/bin/libismagent.so
#8 0x08053c80 in getDotISMLocal ()
#9 0x08053985 in ISMagent ()
#10 0x0804e39f in processSOAPPOSTData ()
#11 0x0804d538 in main ()
#0 0x4069aec6 in CDWARF32Loader::define_files ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#1 0x4069a75b in CDWARF32Loader::Init_Comp_Unit_Prologue ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#2 0x40699fa7 in CDWARF32Loader::InitSrcIter ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#3 0x406998d9 in CDWARF32Loader::GetSrcFileIterator ()
from /opt/intel/vtune/rdc/shared/bin/libdilDWARF32_2.so
#4 0x402e6526 in CFileSymbolBankImpl::LoadLineInfo ()
from /opt/intel/vtune/rdc/shared/bin/libismImpl_2.so
#5 0x4030d9f3 in CFileSymbolBankImpl::CreateISMFile ()
from /opt/intel/vtune/rdc/shared/bin/libismImpl_2.so
#6 0x402c47ff in CAppSymbolBankImpl::AddFileSVEx ()
from /opt/intel/vtune/rdc/shared/bin/libismImpl_2.so
#7 0x402291c0 in GetDotISMLocal ()
from /opt/intel/vtune/rdc/shared/bin/libismagent.so
#8 0x08053c80 in getDotISMLocal ()
#9 0x08053985 in ISMagent ()
#10 0x0804e39f in processSOAPPOSTData ()
#11 0x0804d538 in main ()
Has anyone else seen this / have a workaround?
Installed vtune rpms as follows:
intel-vtune-vtserver-7.2-16940
intel-vtune-ism-7.2-16940
intel-vtune-sampling-rdc-7.2-16940
intel-vtune-lips-2.1-16940
intel-vtune-doc-rdc-7.2-16940
intel-vtune-bistro-2.1-16940
intel-vdk-3.3-99
intel-vtune-ism-7.2-16940
intel-vtune-sampling-rdc-7.2-16940
intel-vtune-lips-2.1-16940
intel-vtune-doc-rdc-7.2-16940
intel-vtune-bistro-2.1-16940
intel-vdk-3.3-99
intel-vdk-src-3.3-99
Regards,
Regards,
Garry.
Message Edited by GazMarsh on 06-13-2005 06:48 AM
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hmm, it appears that the vtserver process has a problem with the debug information present in the .so - stripping the file lets me work around the problem.
Garry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for reporting back what you found!
cheers
jdg
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