On Wed, Feb 19, 2014 at 7:41 AM, Rick McGuire <object.r...@gmail.com> wrote:
> I'm not sure what the requirements for the *ix platforms would be, and I'm
> pretty sure we really don't want to do this for all of the flavors anyway,
> but I'm thinking it might be a useful thing to have a debug version of the
> Windows 32- and 64- bit versions available for download.
>
Yeah, I think so. I was going to suggest to the person that just opened
the bug that I could provide a debug version.
I don't see any reason why we couldn't make it available on SourceForge.
Maybe have a sub-directory named debug to keep the debug version separate
from the other downloads.
> This might allow users that have access to the Visual Studio (and know how
> to use the debugger) to perform some level of crash diagnosis without
> needing to provide a working example they can send us. Sometimes problems
> like this can be diagnosed with nothing more than the stack traceback.
>
I'm not sure what level of support the express version has for the
debugger. I seem to recall the debugger in the express version does not
automatically break in when a program crashes. But, if the user was
motivated enough, he could try running the program under the debugger and
waiting for the crash. He should be able to copy and paste the stack
trace, even if he didn't know how to use the debugger.
I'll put debug versions of the 4.2.0 Windows builds on SourceForge as soon
as I can get to it.
--
Mark Miesfeld
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
