• John Stoneham <captnjameskirk yahoo.com> Mar 17 2009
• Walter Bright <newshound1 digitalmars.com> Mar 17 2009

John Stoneham <captnjameskirk yahoo.com> writes:

Walter Bright Wrote:
 
 http://d.puremagic.com/issues/show_bug.cgi?id=2741


Thanks. (In reply to comment #0)

A few more details if it'll help. Using the gdb command "info sources" on a
simple Tango "hello" program lists the following (comiled with "dmd -g"), which
lists no D source files at all:
/System/Library/Frameworks/System.framework/PrivateHeaders/i386
cpu_capabilities.h, /System/Library/Frameworks/System.framework/PrivateHeaders/machine
cpu_capabilities.h, <command line>, <built-in>,
/SourceCache/Libsystem/Libsystem-88.3.10//, CommPageSymbols.st, {standard input}


Now, the same file compiled with GDC shows the following sources:
/System/Library/Frameworks/System.framework/PrivateHeaders/i386
cpu_capabilities.h, /System/Library/Frameworks/System.framework/PrivateHeaders/machine
cpu_capabilities.h, <command line>, <built-in>,
/SourceCache/Libsystem/Libsystem-88.3.10//, CommPageSymbols.st, {standard
input}, ../shared/rt/typeinfo/ti_C.d, critical.c, arraycast.d,
../shared/rt/util/string.d, ../shared/rt/util/hash.d,
../shared/rt/util/console.d, ../shared/rt/typeinfo/ti_wchar.d,
../shared/rt/typeinfo/ti_void.d, ../shared/rt/typeinfo/ti_ushort.d,
../shared/rt/typeinfo/ti_uint.d, ../shared/rt/typeinfo/ti_ubyte.d,
../shared/rt/typeinfo/ti_short.d, ../shared/rt/typeinfo/ti_int.d,
../shared/rt/typeinfo/ti_dchar.d, ../shared/rt/typeinfo/ti_char.d,
../shared/rt/typeinfo/ti_byte.d, ../shared/rt/typeinfo/ti_Ashort.d,
../shared/rt/typeinfo/ti_Aint.d, ../shared/rt/typeinfo/ti_Ag.d,
../shared/rt/typeinfo/ti_AC.d, monitor.c, memory_dyld.c, memory.d,
/Users/obijohn/projects/d/tango/std/c/stdarg.di, lifetime.d, genobj.d,
gcc/unwind.d, gcc/deh.d, dgccmain2.d, cmain.d, cast.d, aaA.d,
/Users/obijohn/projects/d/hello.d

Also, I took a look at the executable in a hex editor, and in the DMD-compiled
version the main source filename actually comes directly before the path (it
comes after the path in the GDC-compiled version). I don't know if this means
anything, though.

Walter Bright <newshound1 digitalmars.com> writes:

John Stoneham wrote:
 Also, I took a look at the executable in a hex editor, and in the
 DMD-compiled version the main source filename actually comes directly
 before the path (it comes after the path in the GDC-compiled
 version). I don't know if this means anything, though.


Use the dumpobj program that comes with dmd, it'll make it a lot easier 
to examine object files.

Also, anyone can post bug reports and more info to bugzilla!