POV-Ray : Newsgroups : povray.windows : Vs 2017 debug Server Time: 18 Jan 2019 01:53:23 GMT
  Vs 2017 debug (Message 1 to 10 of 11)  
Goto Latest 10 Messages Next 1 Messages >>>
From: Havana7
Subject: Vs 2017 debug
Date: 15 Feb 2018 09:30:01
Message: <web.5a855244b8ec9d993e499bc60@news.povray.org>
I downloaded version 3.7.0 but I can not debug console project. I try to insert
breakpoints in the console project but the window opens but remains black
without any response. Do you have any advice on this? Thank you


Post a reply to this message

From: Kenneth
Subject: Re: Vs 2017 debug
Date: 15 Feb 2018 13:00:01
Message: <web.5a8583a3c588b266a47873e10@news.povray.org>
It is a known problem (or behavior) with #debug and the message window.

#debug "This is my message"
....will NOT show up in the 'messages' window, even though it should do so. It
needs to have a 'line break' at the end   \n  like this:

#debug "This is my message\n"

Here is another example that also works, because it uses more than one #debug:
#debug "This is my message" // no \n  here this time-- but it WILL show up now,
// because the 2nd #debug *does* use \n
#declare FOO = 347.188;
#debug concat("\n","FOO = ", str(FOO,0,3),"\n")

It is complicated! ;-)


Post a reply to this message

From: Kenneth
Subject: Re: Vs 2017 debug
Date: 15 Feb 2018 13:05:00
Message: <web.5a858533c588b266a47873e10@news.povray.org>
Also see this in the newsgroup, for a detailed explanation...

http://news.povray.org/povray.beta-test/thread/%3Cweb.596dfc7892f71496883fb31c0%40news.povray.org%3E/


Post a reply to this message

From: Kenneth
Subject: Re: Vs 2017 debug
Date: 15 Feb 2018 13:15:00
Message: <web.5a858761c588b266a47873e10@news.povray.org>
Or, does you question relate to Visual Studio 2017, while using POV-ray's
'source code'? I apologize if I didn't understand your original message.


Post a reply to this message

From: clipka
Subject: Re: Vs 2017 debug
Date: 15 Feb 2018 17:59:07
Message: <5a85ca6b$1@news.povray.org>
Am 15.02.2018 um 10:26 schrieb Havana7:
> I downloaded version 3.7.0 but I can not debug console project. I try to insert
> breakpoints in the console project but the window opens but remains black
> without any response. Do you have any advice on this? Thank you

I don't think the v3.7.0 console project is even functional.


Post a reply to this message

From: Havana7
Subject: Re: Vs 2017 debug
Date: 16 Feb 2018 07:15:00
Message: <web.5a8684b5c588b2663e499bc60@news.povray.org>
"Kenneth" <kdw### [at] gmailcom> wrote:
> Or, does you question relate to Visual Studio 2017, while using POV-ray's
> 'source code'? I apologize if I didn't understand your original message.

Sorry, but I'm referring to debugging in Visual Studio 2017!


Post a reply to this message

From: Havana7
Subject: Re: Vs 2017 debug
Date: 16 Feb 2018 13:30:01
Message: <web.5a86dc11c588b2663e499bc60@news.povray.org>
clipka <ano### [at] anonymousorg> wrote:
> Am 15.02.2018 um 10:26 schrieb Havana7:
> > I downloaded version 3.7.0 but I can not debug console project. I try to insert
> > breakpoints in the console project but the window opens but remains black
> > without any response. Do you have any advice on this? Thank you
>
> I don't think the v3.7.0 console project is even functional.

Sorry for the error, but I downloaded the master version. I tried with all but
with Visual Studio 2017 Community they do not work.


Post a reply to this message

From: clipka
Subject: Re: Vs 2017 debug
Date: 16 Feb 2018 16:47:16
Message: <5a870b14@news.povray.org>
Am 16.02.2018 um 14:26 schrieb Havana7:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 15.02.2018 um 10:26 schrieb Havana7:
>>> I downloaded version 3.7.0 but I can not debug console project. I try to insert
>>> breakpoints in the console project but the window opens but remains black
>>> without any response. Do you have any advice on this? Thank you
>>
>> I don't think the v3.7.0 console project is even functional.
> 
> Sorry for the error, but I downloaded the master version. I tried with all but
> with Visual Studio 2017 Community they do not work.

- Can you successfully place breakpoints in the GUI version?

- Does the console project run without breakpoints set?

- Can you give me a step-by-step description of what you're actually
doing, i.e. how you're activating the console project in the first
place, where you're setting breakpoints, how you're starting the
project, what parameters you're passing, and whatnot?


I myself am using VS 2015 instead of VS 2017, and haven't touched the
console project in a while (it isn't officially supported), so without
more detailed information, from my point it could be anything from a bug
in VS 2017 to a problem with the console project to a simple user error.


Post a reply to this message

From: Havana7
Subject: Re: Vs 2017 debug
Date: 18 Feb 2018 10:00:01
Message: <web.5a894e6cc588b2663e499bc60@news.povray.org>
> - Can you successfully place breakpoints in the GUI version?

No the window does not open and no breckpoint works

> - Does the console project run without breakpoints set?

No, Only the completely empty command window appears.

> - Can you give me a step-by-step description of what you're actually
> doing, i.e. how you're activating the console project in the first
> place, where you're setting breakpoints, how you're starting the
> project, what parameters you're passing, and whatnot?

I modify the windows / povconfig / syspovconfig.h file by editing the comment in
#define _CONSOLE. Set up console as a startup project, and choose Console
compilation management and deselect GUI.

I have a breackpoint in vfe / win / console / winconsole.cpp Main, I clean the
solution, compile it and start debugging.

Nothing happens.

> I myself am using VS 2015 instead of VS 2017, and haven't touched the
> console project in a while (it isn't officially supported), so without
> more detailed information, from my point it could be anything from a bug
> in VS 2017 to a problem with the console project to a simple user error.

The solution compile the console project perfectly in release mode.

Do you have any suggestions?


Post a reply to this message

From: clipka
Subject: Re: Vs 2017 debug
Date: 18 Feb 2018 12:21:43
Message: <5a896fd7$1@news.povray.org>
Am 18.02.2018 um 10:59 schrieb Havana7:
>> - Can you successfully place breakpoints in the GUI version?
> 
> No the window does not open and no breckpoint works

Can you successfully run the GUI debug version /without/ breakpoints set?

Either way, as long as you are having trouble running or debugging even
the GUI version of POV-Ray, it does not make sense trying to run or
debug the console version.

Since running and debugging the GUI version of POV-Ray in VS 2015 is a
routine thing and I'm not seeing any problems there, I suspect this to
be a problem specific to VS 2017, or even your installation thereof. I'd
therefore recommend seeking assistance from Microsoft or their community.

If running POV-Ray without breakpoints works fine, maybe the breakpoints
do work but the VS 2017 debugger isn't kicking in properly to take you
to the code being executed. That would explain the symptoms you are
reporting.


> I have a breackpoint in vfe / win / console / winconsole.cpp Main, I clean the
> solution, compile it and start debugging.
> 
> Nothing happens.

Try a breakpoint later in the program flow; I'd recommend
`parser_tokenizer.cpp`, about line 2633, right after
`CASE(DEBUG_TOKEN)`. This should cause the breakpoint to only be
triggered when a `#debug` statement in the scene file (or include file)
is encountered.


Post a reply to this message

Goto Latest 10 Messages Next 1 Messages >>>

Copyright 2003-2008 Persistence of Vision Raytracer Pty. Ltd.