That's an error too. What I'd like to see is the stack at the time of the crash, but there's no easy way to do that in Windows unless you've got Visual Studio or something similar installed.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-01-12 05:37: Subject: Re: #include
I don't get an error. The application closes. Unless you want me to dig through the ugly error report that windows gives when an application crashes. But pike gives no error.
"Martin Stjernholm, Roxen IS @ Pike developers forum" 10353@lyskom.lysator.liu.se wrote:> /.../ the -I command crashed pike through the command prompt. (FYI I
am using Windows XP).
What error did you get?
/ Martin Stjernholm, Roxen IS
Previous text:
2004-01-06 16:19: Subject: Re: #include
Actually I have been using. #include "absolute filepath" . I have not enclosed the filename with <>'s since the -I command crashed pike through the command prompt. (FYI I am using Windows XP). As for the poster's original question, I think that perhaps the include path might be incorrect. Try adding the path the include files are in with a -I command argument. That assumes you're using #include
Bill
Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
/ Brevbäraren
Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
/ Brevbäraren