[Issue 14927] GDB cannot be used to debug D programs on OS X

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

Iain Buclaw  changed:

   What|Removed |Added

   Priority|P1  |P2

--

[Issue 14927] GDB cannot be used to debug D programs on OS X

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

Luís Marques  changed:

   What|Removed |Added

 CC||l...@luismarques.eu

--

[Issue 14927] GDB cannot be used to debug D programs on OS X

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

Iain Buclaw ibuc...@gdcproject.org changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||ibuc...@gdcproject.org

--- Comment #1 from Iain Buclaw ibuc...@gdcproject.org ---
 And `info variables` returns the mangled D names for variables and not their 
 real name, despite the language being set to D and doing `demangle 
 [some_name]` returns the correct names.

This is why you must *NEVER* use -gc on Linux/OSX/FreeBSD.  The -gc switch
marks all functions as 'C' language functions, and gdb will not attempt to
demangle such functions when it loads the symbol table.

FYI - there is a PR open that has been dwindling:
https://github.com/D-Programming-Language/dmd/pull/4766

--

[Issue 14927] GDB cannot be used to debug D programs on OS X

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

Iain Buclaw ibuc...@gdcproject.org changed:

   What|Removed |Added

   Keywords||pull

--

[Issue 14927] GDB cannot be used to debug D programs on OS X

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

Iain Buclaw ibuc...@gdcproject.org changed:

   What|Removed |Added

   Assignee|nob...@puremagic.com|ibuc...@gdcproject.org

--

[Issue 14927] GDB cannot be used to debug D programs on OS X

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

--- Comment #2 from Jack Stouffer j...@jackstouffer.com ---
(In reply to Iain Buclaw from comment #1)
 This is why you must *NEVER* use -gc on Linux/OSX/FreeBSD.  The -gc switch
 marks all functions as 'C' language functions, and gdb will not attempt to
 demangle such functions when it loads the symbol table.

Compiling with -g -gs doesn't fix any of the above problems. Doing `info
locals` still responds with No symbol table info available.

--

[Issue 14927] GDB cannot be used to debug D programs on OS X

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

--- Comment #3 from Iain Buclaw ibuc...@gdcproject.org ---
(In reply to Jack Stouffer from comment #2)
 (In reply to Iain Buclaw from comment #1)
  This is why you must *NEVER* use -gc on Linux/OSX/FreeBSD.  The -gc switch
  marks all functions as 'C' language functions, and gdb will not attempt to
  demangle such functions when it loads the symbol table.
 

I wonder if DMD's choice of emitting symbols as _D3foo3bar instead of
__D3foo3bar is biting them on OSX.

--

[Issue 14927] GDB cannot be used to debug D programs on OS X

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14927

David Nadlinger c...@klickverbot.at changed:

   What|Removed |Added

 CC||c...@klickverbot.at

--- Comment #4 from David Nadlinger c...@klickverbot.at ---
(In reply to Iain Buclaw from comment #3)
 (In reply to Jack Stouffer from comment #2)
  (In reply to Iain Buclaw from comment #1)
   This is why you must *NEVER* use -gc on Linux/OSX/FreeBSD.  The -gc switch
   marks all functions as 'C' language functions, and gdb will not attempt to
   demangle such functions when it loads the symbol table.
  
 
 I wonder if DMD's choice of emitting symbols as _D3foo3bar instead of
 __D3foo3bar is biting them on OSX.

It certainly is for the demangling side of things.

--