runtime STATUS ACCESS VIOLATIONS

Christopher Faylor cgf@cygnus.com
Sun Feb 28 23:02:00 GMT 1999


On Sun, Feb 21, 1999 at 12:32:36PM -0600, Murli Ganeshan wrote:
>I have a simple c++ program that generates ACCESS VIOLATIONS at
>runtime. The same code does not generate any runtime errors while
>running the executable generated from djgpp on the same machine. Also,
>there are no runtime errors when compiled on a Linux 2.0.36 box or a
>SUNos 4.1.4 box.
>
>I saw some old postings related to ACCESS VIOLATIONS with malloc and
>the solution was to replace that with mmalloc. Is there a similar one
>for the "new" dynamic memory allocator in c++ that I can use?
>
>Here's a command line snippet.  I would appreciate any
>feedback/suggestions to debug the problem.

Here's some feedback:  Use gdb to debug the problem.  The information
below doesn't provide any information about where the program is dying.
gdb will give you that information.

99.9% of the time this will be due to some kind of programming error
in your code, just like on UNIX.

>
>bash.exe-2.02$ g++ list2.cpp listex2.cxx -o exam
>bash.exe-2.02$ exam
>[main] C:\MSDEV\PROJECTS\HMWK3\EXAM.EXE 1011 (0) handle_exceptions:
>Exception: STATUS_ACCESS_VIOLATION
>[main] EXAM 1011 (0) handle_exceptions: Dumping stack trace to
>EXAM.EXE.core

-- 
cgf@cygnus.com
http://www.cygnus.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com




More information about the Cygwin mailing list