• Jacob Carlborg (13/13) Oct 11 2012 What is actually supposed to work on Mac OS X in regards to debugging
• Sean Kelly (8/11) Oct 15 2012 information. Does this work on any other platform? Is it supposed to be ...
• Jacob Carlborg (4/5) Oct 15 2012 Yeah, I've noticed. Thanks, then I know it's not just me.

Jacob Carlborg <doob me.com> writes:

What is actually supposed to work on Mac OS X in regards to debugging 
and exception?

When an exception is thrown I do get a backtrace but without line 
information. Does this work on any other platform? Is it supposed to be 
working on Mac OS X?

In the debugger, GDB, the only thing that seems to work is getting a 
backtrace. No line numbers and nothing else seems to be possible to do.

I'm using the GDB shipped with Xcode, I do understand that I might need 
to update to a later version but which one? And how should I compile the 
code, with "-gc" or "-g"?

I'm DMD 2.060 on Mac OS X 10.8.2.

-- 
/Jacob Carlborg

Sean Kelly <sean invisibleduck.org> writes:

On Oct 11, 2012, at 12:23 AM, Jacob Carlborg <doob me.com> wrote:

 What is actually supposed to work on Mac OS X in regards to debugging =

and exception?
=20
 When an exception is thrown I do get a backtrace but without line =

information. Does this work on any other platform? Is it supposed to be =
working on Mac OS X?

This is a compiler issue and there are a bunch of tickets for it.  The =
way debug info is generated on OSX has to change.  As things stand, =
debugging on OSX is incredibly painful.  You might be able to get a =
mangled backtrace out of GDB right now, but that's it.=

Jacob Carlborg <doob me.com> writes:

On 2012-10-15 23:41, Sean Kelly wrote:

 This is a compiler issue and there are a bunch of tickets for it.  The way
debug info is generated on OSX has to change.  As things stand, debugging on
OSX is incredibly painful.  You might be able to get a mangled backtrace out of
GDB right now, but that's it.

Yeah, I've noticed. Thanks, then I know it's not just me.

-- 
/Jacob Carlborg