• jicman (8/8) Jul 22 2005 Greetings!
• Ben Hinkle (7/18) Jul 22 2005 Running the app in a debugger should stop at the exception and highlight...

jicman <jicman_member pathlink.com> writes:

Greetings!

Ok, so after Derek explained the "*(new Blah)" vs. "new Blah()", I am asking for
a way of figuring out where in does occurr.  I have three files and the plain
ole,

Error: Access Violation

does not help me much.  Any ideas how to figure out where this is happening?

thanks,

josé

"Ben Hinkle" <ben.hinkle gmail.com> writes:

"jicman" <jicman_member pathlink.com> wrote in message 
news:dbr0v1$17e4$1 digitaldaemon.com...
 Greetings!

 Ok, so after Derek explained the "*(new Blah)" vs. "new Blah()", I am 
 asking for
 a way of figuring out where in does occurr.  I have three files and the 
 plain
 ole,

 Error: Access Violation

 does not help me much.  Any ideas how to figure out where this is 
 happening?

 thanks,

 josé

Running the app in a debugger should stop at the exception and highlight the 
line (or at least give you a stack trace). What platform are you on? On 
Windows I use the ancient WinDbg that understands D data structures.
Or if the debugger route isn't working use a few well-placed writefln's to 
watch it run.