- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi,
i am running fedora 12.
my kernel is: 2.6.31.6-166.fc12.x86_64 #1 SMP Wed Dec 9 10:46:22 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
my icpc is: icpc (ICC) 11.1 20091130
while trying to debug my c++ application i received the following from the idb:
Intel Debugger for applications running on Intel 64, Build [1.2097.2.319]
------------------
object file name: helix
Reading symbols from /home/ofer/projects/hts_v3. option_main.new_sched/helix/ x86_64/bin/debug/helix...done.
Intel Debugger for applications running on Intel 64 caught signal "Segmentation fault" (11).
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
/lib64/libc.so.6() [0x3dc0432730]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf219emitSTFor DIETypedefERK12AttrBindings+ 0x184) [0xad5e8c]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf212emitSTFor DIEER11WalkCtxDIEsbRK12AttrBin dings+0x33d) [0xac3b9f]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf214walkTreeO fDIEsER11WalkCtxDIEs+0xd4) [0xac8678]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf217walkChild renOfDIEER11WalkCtxDIEsRK12Att rBindings+0x8f) [0xac8559]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf225walkChild renOfCurrentTypeER11WalkCtxDIE sRK12AttrBindingsP4Type+0x31) [0xac452b]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf226emitSTFor DIESubroutineTypeER11WalkCtxDI EsRK12AttrBindings+0x12d) [0xad5c89]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf212emitSTFor DIEER11WalkCtxDIEsbRK12AttrBin dings+0x355) [0xac3bb7]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf214walkTreeO fDIEsER11WalkCtxDIEs+0xd4) [0xac8678]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf217walkChild renOfDIEER11WalkCtxDIEsRK12Att rBindings+0x8f) [0xac8559]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf227emitSTFor DIECompilationUnitER11WalkCtxD IEsbRK12AttrBindings+0x389) [0xaca30f]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf212emitSTFor DIEER11WalkCtxDIEsbRK12AttrBin dings+0x3a4) [0xac3c06]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf214walkTreeO fDIEsER11WalkCtxDIEs+0xd4) [0xac8678]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf211readSymbo lsE19ParseSyms_ ReadLevelP7FileLocP6SymLoc+ 0x343) [0xabcc41]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN15ParseSymsDwarf215readFullS ymbolsEP7FileLocP6SymLoc+0x14) [0xabd0b4]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN6SymLoc6readItEv+0x2b) [0xb01acf]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN6Symbol28completeOneSymbolIf NecessaryEv+0x52) [0xafb466]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN6Symbol19completeIfNecessary Ev+0x10) [0xafb336]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN6Symbol7varietyEv+0x15) [0xafb889]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ Z19symbolRelocatedAddrP6Symbol P9AddrSpaceRbR13RelocatedAddr+ 0xb9) [0x7a1be9]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN33ProcedureDescriptorHeurist icEM64T24hiAddressBasedOnNextP rocEP14ReadableSymtabP9AddrSpa ceP14SymbolEntrydefRK13Relocat edAddr+0x6c) [0x703164]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN33ProcedureDescriptorHeurist icEM64T5guessEv+0x385) [0x7029b5]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN33ProcedureDescriptorHeurist icEM64T10prologSizeEP9AddrSpac eRK13RelocatedAddr+0xc) [0x715636]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN22ProcedureDescriptorDef27po sitionWithRespectToPrologEP9Ad drSpaceRK13RelocatedAddrRP14Sy mbolEntrydefR27PositionWithRes pectToPrologRS2_SA_SA_SA_+ 0x4e) [0x70a1dc]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN11SessionBase12setCurrScopeE P5Scope+0x221) [0x67ba29]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN11SessionBase12setCurrScopeE P6Symbol+0xec) [0x67b7ec]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN7Session13SetDbgVarMainEb+ 0xc2) [0x880f4e]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN7Session17setInitialContextE v+0x54) [0x8871d0]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN7Session13switchContextEP7Pr ocess+0x55) [0x880e15]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN11SessionBase17startLocalPro cessEP3JobP7ArgList22IsOrIsNot ADummyProcess+0xb6) [0x67becc]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ Z17StartDummyProcessP3Job+ 0x63) [0x7ba469]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN7CmdLoad5do_ itER19CmdExecutionContextRN10B aseForCmd9CmdResultE+0x21e) [0x7b9794]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN10BaseForCmd7executeEb+ 0xe7b) [0x7fd5d3]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN3Cmd20executeAsInternalCmdEv +0x23) [0x7b49a5]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZN12InitialState10executeCmdEv +0x44) [0x888ac8]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ Z15decladebug_initiPPKcS1_+ 0x8b5) [0x5ecc99]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ Z7idbMainiPPKcS1_+0x199) [0x5e979f]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(main+0x3c) [0x5e8800]
/lib64/libc.so.6(__libc_start_ main+0xfd) [0x3dc041eb1d]
/opt/intel/Compiler/11.1/064/ bin/intel64/iidb(_ ZStlsISt11char_ traitsIcEERSt13basic_ ostreamIcT_ES5_c+0x62) [0x5e872a]
Could not start process for helix
No image loaded ... Recovering ...
(idb)
any help will be appreciated,
thanks in advance,
ofer
i am running fedora 12.
my kernel is: 2.6.31.6-166.fc12.x86_64 #1 SMP Wed Dec 9 10:46:22 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
my icpc is: icpc (ICC) 11.1 20091130
while trying to debug my c++ application i received the following from the idb:
Intel Debugger for applications running on Intel 64, Build [1.2097.2.319]
------------------
object file name: helix
Reading symbols from /home/ofer/projects/hts_v3.
Intel Debugger for applications running on Intel 64 caught signal "Segmentation fault" (11).
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
/lib64/libc.so.6() [0x3dc0432730]
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/opt/intel/Compiler/11.1/064/
/lib64/libc.so.6(__libc_start_
/opt/intel/Compiler/11.1/064/
Could not start process for helix
No image loaded ... Recovering ...
(idb)
any help will be appreciated,
thanks in advance,
ofer
Link Copied
7 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ofer,
I appreciate you reporting this. Thanks for the detailed call trace and background info on the segmentation fault. The problem seems to be with the symbol info parser in the debugger.This could be due to sloppy symbol info with compiler optimizations. Regardless, the debugger needs to handle such a scenario more gracefully and allow you to continue debugging. I am afraid the one additional thing we will need to clearly identify the root cause for it and come up with a workaround and/or fix is a way to reproduce it.
Can you share the very helix object you were trying to debug? Just the ELF Dwarf2 executable is good enough. No sources needed. I appreciate you reporting this. Thanks for the detailed call trace and background info on the segmentation fault. The problem seems to be with the symbol info parser in the debugger.This could be due to sloppy symbol info with compiler optimizations. Regardless, the debugger needs to handle such a scenario more gracefully and allow you to continue debugging. I am afraid the one additional thing we will need to clearly identify the root cause for it and come up with a workaround and/or fix is a way to reproduce it.
Thanks, Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Robert MuellerAlbrecht (Intel)
Hi Ofer,
I appreciate you reporting this. Thanks for the detailed call trace and background info on the segmentation fault. The problem seems to be with the symbol info parser in the debugger.This could be due to sloppy symbol info with compiler optimizations. Regardless, the debugger needs to handle such a scenario more gracefully and allow you to continue debugging. I am afraid the one additional thing we will need to clearly identify the root cause for it and come up with a workaround and/or fix is a way to reproduce it.
Can you share the very helix object you were trying to debug? Just the ELF Dwarf2 executable is good enough. No sources needed. I appreciate you reporting this. Thanks for the detailed call trace and background info on the segmentation fault. The problem seems to be with the symbol info parser in the debugger.This could be due to sloppy symbol info with compiler optimizations. Regardless, the debugger needs to handle such a scenario more gracefully and allow you to continue debugging. I am afraid the one additional thing we will need to clearly identify the root cause for it and come up with a workaround and/or fix is a way to reproduce it.
Thanks, Rob
thanks for your reply.
the bzip2 elf dwarf2 executable is of size .8650081 bytes. where / how to send it to you?
thanks in advance,
ofer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
http://software.intel.com/en-us/forums/showannouncement.php?a=78
gives detailed instructions for attaching here, or you could make a report on premier.intel.com and attach there, referring to your thread on this forum.
gives detailed instructions for attaching here, or you could make a report on premier.intel.com and attach there, referring to your thread on this forum.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - tim18
http://software.intel.com/en-us/forums/showannouncement.php?a=78
gives detailed instructions for attaching here, or you could make a report on premier.intel.com and attach there, referring to your thread on this forum.
gives detailed instructions for attaching here, or you could make a report on premier.intel.com and attach there, referring to your thread on this forum.
here is the attached bzip2 elf dwarf2 executable.
thanks again,
ofer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - tim18
http://software.intel.com/en-us/forums/showannouncement.php?a=78
gives detailed instructions for attaching here, or you could make a report on premier.intel.com and attach there, referring to your thread on this forum.
gives detailed instructions for attaching here, or you could make a report on premier.intel.com and attach there, referring to your thread on this forum.
Thanks Ofer - great - I am downloading it right now and will let you know hwat I find out.
Thanks, Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ofer,
I was easily able to reproduce the issue. This is quite certainly an issue in the symbol info parser of our debugger. I escalated it and filed defect DPD200149096 for it in our database. I will keep you posted when it is fixed.
I was easily able to reproduce the issue. This is quite certainly an issue in the symbol info parser of our debugger. I escalated it and filed defect DPD200149096 for it in our database. I will keep you posted when it is fixed.
Thanks, Rob
P.S. As a workaround I would suggest looking at debugging without or with less optimizations enabled in your build.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ofer,
I wanted to let you know that we identified the problem in the debugger with your executable and we also found a fix for it. It has been checked into our codebase and should thus be part of the next Compiler Pro release.
Thanks, Rob
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