• sdvcn (12/12) Nov 06 2014 [code]
• sdvcn (4/16) Nov 06 2014 visual d ver:0.3.39
• Rainer Schuetze (6/18) Nov 07 2014 I can reproduce, it is very likely a bug. The line number info of the

"sdvcn" <sdvcn 126.com> writes:

[code]
import std.stdio;

struct awaw{
	string a1; //  <--
}

int main(string[] argv)
{
     writeln("Hello D-World!"); // <---BP
     return 0;
}

[/code]

remove string(a1) for struct ,bp of stop

"sdvcn" <sdvcn 126.com> writes:

On Thursday, 6 November 2014 at 12:18:56 UTC, sdvcn wrote:
 [code]
 import std.stdio;

 struct awaw{
 	string a1; //  <--
 }

 int main(string[] argv)
 {
     writeln("Hello D-World!"); // <---BP
     return 0;
 }

 [/code]

 remove string(a1) for struct ,bp of stop

visual d ver:0.3.39
dmd ver:2.066.1
cv2pdb ver:0.32

Rainer Schuetze <r.sagitario gmx.de> writes:

On 06.11.2014 13:18, sdvcn wrote:
 [code]
 import std.stdio;

 struct awaw{
      string a1; //  <--
 }

 int main(string[] argv)
 {
      writeln("Hello D-World!"); // <---BP
      return 0;
 }

 [/code]

 remove string(a1) for struct ,bp of stop

I can reproduce, it is very likely a bug. The line number info of the 
implicitely generated functions __xtoHash and __xopEquals for structs 
overlap with the main function, and this seems to confuse the VS debugger.

Switching to the mago debug engine seems fine, breakpoints work there. 
This suggests a problem in cv2pdb...