www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - DerelictGL3.reload(); crashes in release mode, but not in debug

reply Dennis <dkorpel gmail.com> writes:
I'm trying to set up a game window with Derelict glfw and opengl.
When I perform a default (debug) build, it correctly shows a 
window, but when I do this:
dub run "--build=release"

Then I get this:

object.Error (0): Access Violation
----------------
0x00443BCF
0x00425164
0x00418545
0x00418874
0xF96485C7
0x83ACFFFF
0x85C70041
0xFFFFF960
Program exited with code 1

With some writeln calls I found that it happens in 
DerelictGL3.reload():

writeln(__LINE__); //printed before error
DerelictGL3.reload();
writeln(__LINE__); //not printed

But I have no idea how to further debug this. Any suggestions 
what I can do?
Nov 18 2017
parent reply Mike Parker <aldacron gmail.com> writes:
On Saturday, 18 November 2017 at 12:36:36 UTC, Dennis wrote:
 I'm trying to set up a game window with Derelict glfw and 
 opengl.
 When I perform a default (debug) build, it correctly shows a 
 window, but when I do this:
 dub run "--build=release"

 Then I get this:

 object.Error (0): Access Violation
 ----------------
 0x00443BCF
 0x00425164
 0x00418545
 0x00418874
 0xF96485C7
 0x83ACFFFF
 0x85C70041
 0xFFFFF960
 Program exited with code 1

 With some writeln calls I found that it happens in 
 DerelictGL3.reload():

 writeln(__LINE__); //printed before error
 DerelictGL3.reload();
 writeln(__LINE__); //not printed

 But I have no idea how to further debug this. Any suggestions 
 what I can do?
The proper place to report this sort of issue is at the DerelictGL3 issues page [1]. You'll also want to include some minimal, reproducible sample code.
Nov 18 2017
next sibling parent Mike Parker <aldacron gmail.com> writes:
On Saturday, 18 November 2017 at 14:15:21 UTC, Mike Parker wrote:
 The proper place to report this sort of issue is at the 
 DerelictGL3 issues page [1]. You'll also want to include some 
 minimal, reproducible sample code.
[1] https://github.com/DerelictOrg/DerelictGL3/issues
Nov 18 2017
prev sibling parent Dennis <dkorpel gmail.com> writes:
On Saturday, 18 November 2017 at 14:15:21 UTC, Mike Parker wrote:
 The proper place to report this sort of issue is at the 
 DerelictGL3 issues page [1]. You'll also want to include some 
 minimal, reproducible sample code.
Okay, I've made an issue: https://github.com/DerelictOrg/DerelictGL3/issues/59
Nov 18 2017