Am Fri, 05 Feb 2016 11:06:16 +0000 schrieb Vadim Lopatin <coolreader....@gmail.com>:
> On Wednesday, 3 February 2016 at 13:50:56 UTC, Johannes Pfau > wrote: > > (Pre-)Alpha quality binaries are available, but we don't want to > > advertise these on the homepage: > > ftp://ftp.gdcproject.org/binaries/5.2.0/x86_64-w64-mingw32/gdc-5.2.0+2.066.1.7z > > ftp://ftp.gdcproject.org/binaries/5.2.0/i686-w64-mingw32/gdc-5.2.0+2.066.1.7z > > > > Binaries generated by GDC/mingw have a problem with debugging > using GDB. > > Setting of breakpoints, stepping by lines work ok. > > Showing of local variables for frame works strange > > -stack-list-variables --thread 1 --frame 0 --simple-values > > Instead of locals, I see a list of some global static variables, > like typeinfo and init values, e.g.: > > variables = [ > { > name = > "5TypeInfo_S4core8demangle16__T6mangleTFZPvZ6mangleFNaNbNfAxaAaZ11DotSplitte()", > type = "TypeInfo_Struct" > }, > { > name = > "std.uni.SliceOverIndexed!(int[]).SliceOverIndexed.__init", > type = "const struct SliceOverIndexed" > }, > > No local variables are shown. > > Is it GDC or GDB issue? > Could be both. I don't think the GDB/GDC combination has been tested on windows. You should use a very recent GDB version for the GCC5 builds though. http://msys2.github.io/ provides a mingw-w64-gdb 7.10.1 package.
