Thread overview | |||||
---|---|---|---|---|---|
|
November 06, 2014 this IS bug? bp not stop? | ||||
---|---|---|---|---|
| ||||
[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 |
November 06, 2014 Re: this IS bug? bp not stop? | ||||
---|---|---|---|---|
| ||||
Posted in reply to sdvcn | 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
|
November 07, 2014 Re: this IS bug? bp not stop? | ||||
---|---|---|---|---|
| ||||
Posted in reply to sdvcn |
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...
|
Copyright © 1999-2021 by the D Language Foundation