[Issue 3657] No lexical scope for local variables in debug info
https://issues.dlang.org/show_bug.cgi?id=3657 --- Comment #17 from Manu --- Thank god! --
[Issue 3657] No lexical scope for local variables in debug info
https://issues.dlang.org/show_bug.cgi?id=3657 --- Comment #18 from Manu --- Only 7 years later ;) --
[Issue 3657] No lexical scope for local variables in debug info
https://issues.dlang.org/show_bug.cgi?id=3657 --- Comment #16 from github-bugzi...@puremagic.com --- Commit pushed to stable at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/301a9ac2d27ed5524a0dafdd7ece43166502949b Merge pull request #2867 from rainers/cv_lexicalscope --
[Issue 3657] No lexical scope for local variables in debug info
https://issues.dlang.org/show_bug.cgi?id=3657 --- Comment #15 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/301a9ac2d27ed5524a0dafdd7ece43166502949b Merge pull request #2867 from rainers/cv_lexicalscope fix issue 3657: add lexical scope to CodeView debug info --
[Issue 3657] No lexical scope for local variables in debug info
https://issues.dlang.org/show_bug.cgi?id=3657 --- Comment #14 from Manu --- Where does this stand? I thought this was fixed recently? --
[Issue 3657] No lexical scope for local variables in debug info
https://issues.dlang.org/show_bug.cgi?id=3657 Andrei Alexandrescu changed: What|Removed |Added Version|unspecified |D2 --
[Issue 3657] No lexical scope for local variables in debug info
https://issues.dlang.org/show_bug.cgi?id=3657 Rainer Schuetze changed: What|Removed |Added CC||turkey...@gmail.com --- Comment #13 from Rainer Schuetze --- *** Issue 12244 has been marked as a duplicate of this issue. *** --
[Issue 3657] No lexical scope for local variables in debug info
https://d.puremagic.com/issues/show_bug.cgi?id=3657 Rainer Schuetze changed: What|Removed |Added Keywords|patch |pull --- Comment #12 from Rainer Schuetze 2013-11-23 09:28:31 PST --- I figured optlink is doing fine, it was mostly a missing relocation that made the patch fail for S_BLOCK32/S_END. Resurrectd and fixed the patch: https://github.com/D-Programming-Language/dmd/pull/2867 -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
https://d.puremagic.com/issues/show_bug.cgi?id=3657 --- Comment #11 from Rainer Schuetze 2013-11-23 02:58:26 PST --- (In reply to comment #10) > I think that it's unlikely that the linker will be considerably improved at > this point. > > Barring merging cv2pdb into DMD, would it make sense to add a -gp switch, > which > would cause DMD to emit debug information with cv2pdb extensions? I just noticed that optlink has support for S_BLOCK32/S_END, it might just be broken. I'll have a closer look... -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
https://d.puremagic.com/issues/show_bug.cgi?id=3657 Vladimir Panteleev changed: What|Removed |Added CC||thecybersha...@gmail.com --- Comment #10 from Vladimir Panteleev 2013-11-21 05:45:00 EET --- I think that it's unlikely that the linker will be considerably improved at this point. Barring merging cv2pdb into DMD, would it make sense to add a -gp switch, which would cause DMD to emit debug information with cv2pdb extensions? -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
https://d.puremagic.com/issues/show_bug.cgi?id=3657 pravic changed: What|Removed |Added CC||ehy...@gmail.com --- Comment #9 from pravic 2013-11-18 00:25:05 PST --- *** Issue 11516 has been marked as a duplicate of this issue. *** -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 --- Comment #8 from Walter Bright 2012-01-21 13:56:03 PST --- Maybe we should defer this then until the linker can be improved. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 --- Comment #7 from Rainer Schuetze 2012-01-21 13:49:51 PST --- So I guess we are kind of stuck. Is it really much worse than all the temporaries generated as local variables by dmd? Do you see another possibility to pass variable life time information to the debugger? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 --- Comment #5 from Rainer Schuetze 2012-01-20 00:31:22 PST --- So you are fine with the workaround to emit symbols to be translated back to the block statements? This will create strange symbols "@sblk" and "@send" if you happen to work with the debug info without using cv2pdb. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 --- Comment #4 from Walter Bright 2012-01-19 17:56:43 PST --- That would be a great deal of work, mainly because the optlink codeview code is a giant inscrutable mess. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 --- Comment #3 from Rainer Schuetze 2012-01-19 13:42:22 PST --- I'd like to if there is a chance to avoid the ugly workaround regarding optlink: Will it be a large issue to add support for S_BLOCK32/S_END debug entries to optlink? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #2 from Walter Bright 2012-01-18 20:55:44 PST --- Want to do a pull request for this? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 Rainer Schuetze changed: What|Removed |Added Keywords||patch Priority|P2 |P3 -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3657] No lexical scope for local variables in debug info
http://d.puremagic.com/issues/show_bug.cgi?id=3657 --- Comment #1 from Rainer Schuetze 2009-12-29 02:57:56 PST --- Created an attachment (id=536) add lexical scope to local symbols in codeview debug info The patch consists of two parts: 1. modify the parser to remember the end of scope statements. 2. transfer the life-time info to the debug info. The latter is straight forward, but the second part is a bit complicated. As scoping information is lost in the code generation, only the line of declaration and the end of the enclosing scope is remembered by the symbol. The life-time of the variable in terms of code byte offset and length is then reconstructed from the line number info. This is only implemented for CodeView information, as I don't know anything about the other formats. Another complication: optlink removes the corresponding debug entries, so I had to use pseudo-symbols to get this info to cv2pdb and convert them back there. This might confuse other tools, so maybe this feature should be enabled by some command line switch only. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
