digitalmars.D.debugger - Debug variables showing when not in scope in Visual D
- Michelle Long (11/11) Oct 28 2018 Debug variables are showing when not in scope. Is it possible to
- Rainer Schuetze (3/20) Oct 29 2018 That used to work for dmd, but it seems to have regressed (still works
- Rainer Schuetze (4/28) Oct 29 2018 Sorry, I slightly misremembered. The respective debug information is
- Michelle Long (9/43) Oct 30 2018 Can Visual D detect scopes while debugging? E.g., if one is at
- Rainer Schuetze (3/49) Nov 03 2018 I'd consider it a dmd issue and created an enhancement request:
Debug variables are showing when not in scope. Is it possible to remove them? They also show before they are actually defined in the source code. int x = 0; < BP here, y and z are shown in the locals. int y = 3; { int z = 4; } // z is when when here. One ends up with a huge list of variables of all the locals when they don't even "exist". I'm using the Mago debugger.
Oct 28 2018
On 28/10/2018 18:35, Michelle Long wrote:Debug variables are showing when not in scope. Is it possible to remove them? They also show before they are actually defined in the source code. int x = 0; < BP here, y and z are shown in the locals. int y = 3; { int z = 4; } // z is when when here. One ends up with a huge list of variables of all the locals when they don't even "exist". I'm using the Mago debugger.That used to work for dmd, but it seems to have regressed (still works for try/catch blocks). IIRC LDC does not emit appropriate debug information.
Oct 29 2018
On 29/10/2018 08:32, Rainer Schuetze wrote:On 28/10/2018 18:35, Michelle Long wrote:Sorry, I slightly misremembered. The respective debug information is only emitted by dmd if there are multiple declarations with the same variables in different scopes in the same function. This still works fine.Debug variables are showing when not in scope. Is it possible to remove them? They also show before they are actually defined in the source code. int x = 0; < BP here, y and z are shown in the locals. int y = 3; { int z = 4; } // z is when when here. One ends up with a huge list of variables of all the locals when they don't even "exist". I'm using the Mago debugger.That used to work for dmd, but it seems to have regressed (still works for try/catch blocks). IIRC LDC does not emit appropriate debug information.
Oct 29 2018
On Monday, 29 October 2018 at 07:39:14 UTC, Rainer Schuetze wrote:On 29/10/2018 08:32, Rainer Schuetze wrote:Can Visual D detect scopes while debugging? E.g., if one is at some line can it determine properly the scope of things? e.g., what symbol is in the current scope and what is not? Or is this all up to dmd? If dmd is the cause of most of these debugging issues, should dmd give as much info as it can so the debugging experience can be optimal? It makes no sense for a compiler to make the debugging experience more difficult because debugging is naturally part of the equation.On 28/10/2018 18:35, Michelle Long wrote:Sorry, I slightly misremembered. The respective debug information is only emitted by dmd if there are multiple declarations with the same variables in different scopes in the same function. This still works fine.Debug variables are showing when not in scope. Is it possible to remove them? They also show before they are actually defined in the source code. int x = 0; < BP here, y and z are shown in the locals. int y = 3; { int z = 4; } // z is when when here. One ends up with a huge list of variables of all the locals when they don't even "exist". I'm using the Mago debugger.That used to work for dmd, but it seems to have regressed (still works for try/catch blocks). IIRC LDC does not emit appropriate debug information.
Oct 30 2018
On 30/10/2018 16:38, Michelle Long wrote:On Monday, 29 October 2018 at 07:39:14 UTC, Rainer Schuetze wrote:I'd consider it a dmd issue and created an enhancement request: https://issues.dlang.org/show_bug.cgi?id=19349On 29/10/2018 08:32, Rainer Schuetze wrote:Can Visual D detect scopes while debugging? E.g., if one is at some line can it determine properly the scope of things? e.g., what symbol is in the current scope and what is not? Or is this all up to dmd? If dmd is the cause of most of these debugging issues, should dmd give as much info as it can so the debugging experience can be optimal? It makes no sense for a compiler to make the debugging experience more difficult because debugging is naturally part of the equation.On 28/10/2018 18:35, Michelle Long wrote:Sorry, I slightly misremembered. The respective debug information is only emitted by dmd if there are multiple declarations with the same variables in different scopes in the same function. This still works fine.Debug variables are showing when not in scope. Is it possible to remove them? They also show before they are actually defined in the source code. int x = 0; < BP here, y and z are shown in the locals. int y = 3; { int z = 4; } // z is when when here. One ends up with a huge list of variables of all the locals when they don't even "exist". I'm using the Mago debugger.That used to work for dmd, but it seems to have regressed (still works for try/catch blocks). IIRC LDC does not emit appropriate debug information.
Nov 03 2018