This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Status Access Violation
- To: gnu-win32 at cygnus dot com
- Subject: Re: Status Access Violation
- From: cgf at bbc dot com (Christopher Faylor)
- Date: Sat, 27 Dec 1997 21:16:15 GMT
- Organization: Boston Business Computing, Ltd.
- References: <001901bd1254$122c7c20$c632a5ce@primenet.primenet.com>
- Reply-To: cgf at bbc dot com
In article <001901bd1254$122c7c20$c632a5ce@primenet.primenet.com>,
Dan Lundy <dlundy@primenet.com> wrote:
>-=-=-=-=-=-
>
>I have scaned the archives extensively without success. You know the problem,
>
>STATUS ACCESS VIOLATION.
>
>I have read a couple of potential fixes, and have attempted them
>without success.
>
>If you have had similar problems under Win95, and have found an
>appropriate method to cure this problem, please provide me with the
>details.
>
>dlundy@primenet.com
Compile the program with the the -g option and use gdb to debug it
just like you would any other program. STATUS ACCESS VIOLATION means
that you are accessing memory that you shouldn't be. Possibly you are
accessing a pointer with garbage in it.
This is no mystery. The answer on how to debug problems with your program
is almost always going to be "run it under a debugger". That's why debuggers
were invented.
--
http://www.bbc.com/ cgf@bbc.com "Strange how unreal
VMS=>UNIX Solutions Boston Business Computing the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".