• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
DWARF debugging issue: DW_FORM_strp pointing outside of .debug_str section
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

DWARF debugging issue: DW_FORM_strp pointing outside of .debug_str section


  • Subject: DWARF debugging issue: DW_FORM_strp pointing outside of .debug_str section
  • From: Ladd Van Tol <email@hidden>
  • Date: Tue, 1 Aug 2006 12:17:27 -0700

I am doing some debugging of a fairly large C++ project with numerous frameworks and static libraries. I started running into some odd debugging issues while using Stabs, so I decided to try DWARF. Unfortunately, the problems are worse under DWARF, with the debugger spitting console messages like this:

warning: .o file "/Users/ladd/Code/CPS/foo/trunk/build/Output/XCode/ Debug/libBar.a(monkey.o)" more recent than executable timestamp
DW_FORM_strp pointing outside of .debug_str section [in module /Users/ ladd/Code/CPS/foo/trunk/build/Output/XCode/Debug/Banana.framework/ Versions/A/Banana]


The library names are changed to protect the innocent, but "libBar.a" is linked into "Banana.framework". After this message, the debugger generally goes out to lunch, and either exits immediately, or stops stepping properly

An examination of the timestamps reveals that things should be OK:

> ls -l /Users/ladd/Code/CPS/foo/trunk/build/Output/XCode/Debug/ libBar.a
-rw-r--r-- 1 ladd ladd 4579332 Aug 1 12:01 /Users/ladd/Code/CPS/ foo/trunk/build/Output/XCode/Debug/libBar.a


> ls -l /Users/ladd/Code/CPS/foo/trunk/build/Output/XCode/Debug/ Banana.framework/Versions/A/Banana
-rwxr-xr-x 1 ladd ladd 31635492 Aug 1 12:03 /Users/ladd/Code/CPS/ foo/trunk/build/Output/XCode/Debug/Banana.framework/Versions/A/Banana


This project ultimately runs as a Safari plugin, so it is possible that the executable timestamp message is just gdb getting confused.

I would file a bug on this, but I cannot reproduce this situation with a smaller project, and I cannot provide source for the project where the problem occurs.

Anyone else seen anything similar? Any solutions?

Thanks,

	Ladd

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Problems with hdiutil
  • Next by Date: Debugger stops at Program Loaded
  • Previous by thread: Re: Problems with hdiutil
  • Next by thread: Debugger stops at Program Loaded
  • Index(es):
    • Date
    • Thread