[Issue 18882] __gshared not displaying in debuginfo

2020-03-07 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

Rainer Schuetze  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Rainer Schuetze  ---
Finally got around to implement the cache for global symbols, see
https://github.com/dlang/visuald/releases/tag/v0.52.0-beta1

--


[Issue 18882] __gshared not displaying in debuginfo

2019-06-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

Walter Bright  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=17675

--


[Issue 18882] __gshared not displaying in debuginfo

2019-06-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

Walter Bright  changed:

   What|Removed |Added

   Keywords||symdeb
 CC||bugzi...@digitalmars.com

--


[Issue 18882] __gshared not displaying in debuginfo

2018-05-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

--- Comment #4 from Rainer Schuetze  ---
The debug info contains the "pretty" name, i.e. the fully qualified name, even
for extern(C++) symbols. Otherwise you would have to guess the linkage and type
as it is part of the mangled name.

What could be possible is to inspect all symbol at startup and create a map
using the unqualified name as key. That might have a number of conflicts,
though.

--


[Issue 18882] __gshared not displaying in debuginfo

2018-05-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

--- Comment #3 from Manu  ---
Hmm... yeah, that's unfortunate.

I don't understand why it's hard to resolve the name. It's extern(C++), and it
has no namespace supplied, so the correct symbol name should just be the
mangled name, with no scope or anything.

How is it that qualified names (with the D scope) can find a C++ symbol? The
C++ symbol has no concept of D scope. Why does it need to be given a scope at
all?

--


[Issue 18882] __gshared not displaying in debuginfo

2018-05-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

--- Comment #2 from Rainer Schuetze  ---
See also issue 11024: there is no information about imports in the debug
informations so you don't know which symbols are visible in the current scope
and what their qualified name is.

In D functions, the qualified name is used to find the requested symbol, too.
This fails for extern(C/C++) functions that don't have the qualification, or if
the symbol is in another module.

You can still watch the variable using the fully qualified name (even for
extern(C++) symbols), e.g. "dmd.globals.global". This actually matches C++
symbols that are in namespaces which also have to be specified.

--


[Issue 18882] __gshared not displaying in debuginfo

2018-05-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

--- Comment #1 from Manu  ---
Perhaps it's the extern(C++) that's the problem?

That would explain why I have debug problems a lot.

--


[Issue 18882] __gshared not displaying in debuginfo

2018-05-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18882

Manu  changed:

   What|Removed |Added

   Assignee|nob...@puremagic.com|r.sagita...@gmx.de

--