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

Martin Nowak <code@dawg.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |code@dawg.eu

--- Comment #1 from Martin Nowak <code@dawg.eu> ---
We have that since ages, during a debug session when accessing a variable the address jumps to the declaration of that variable. I guess there is even an existing but report for that.

--

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

--- Comment #2 from yazan.dabain@gmail.com ---
I fear that, as now file/line info show in backtraces, these bugs will be more annoying and prevalent.

--

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

--- Comment #3 from yazan.dabain@gmail.com ---
I am sure there is a lot of other cases too.

--

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

Timothee Cour <timothee.cour2@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |timothee.cour2@gmail.com

--- Comment #4 from Timothee Cour <timothee.cour2@gmail.com> ---
I was going to write a bug report regarding a similar issue I had and found this bug.

Any update on that?

My observations:
* wrong line numbers (off by 1 or more) are shown when debugging with lldb and
compiling with dmd -g
* ldc doesn't have this issue

--

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

Rainer Schuetze <r.sagitario@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |symdeb
                 CC|                            |r.sagitario@gmx.de

--

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

LucienPe <lucien.perregaux@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |lucien.perregaux@gmail.com
         Resolution|---                         |FIXED

--- Comment #5 from LucienPe <lucien.perregaux@gmail.com> ---
Seems to be fixed for a while, but I couldn't find the commit which fixed it.

--