public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jonathan George <outlaw@terraworld.net>
To: gnu-win32@cygnus.com
Subject: problems reading/writing to files?
Date: Sat, 11 Jul 1998 04:23:00 -0000	[thread overview]
Message-ID: <3.0.5.32.19980711005355.00944100@terraworld.net> (raw)

Hello all!

I'm compiling a program using cygwin b19.1, (gcc -o lite lite.c).

The compile goes smoothly (no errors), yet when I run the program it seems
to core dump everytime it tries to either READ or WRITE to a file (using
fprintf and/or fgets...

Here is the core:

(D:\LITE\LITE.EXE 1000) Exception trapped!
(D:\LITE\LITE.EXE 1000)
exception C0000005 at 4011A3
(D:\LITE\LITE.EXE 1000) exception: ax 401040
bx 0 cx 3 dx BFFBFA00
(D:\LITE\LITE.EXE 1000) exception: si 253FCA8 di
81587520 bp 253FC84 sp 253FA70
(D:\LITE\LITE.EXE 1000) exception is:
STATUS_ACCESS_VIOLATION
(D:\LITE\LITE.EXE 1000) Stack
trace:
(D:\LITE\LITE.EXE 1000) frame 0: sp = 0x253F780, pc =
0x1000A250
(D:\LITE\LITE.EXE 1000) frame 1: sp = 0x253F8A4, pc =
0xBFF76780
(D:\LITE\LITE.EXE 1000) frame 2: sp = 0x253F8C8, pc =
0xBFF858F3
(D:\LITE\LITE.EXE 1000) frame 3: sp = 0x253F960, pc =
0xFFECBAD7
(D:\LITE\LITE.EXE 1000) frame 4: sp = 0x253FC84, pc =
0x401921
(D:\LITE\LITE.EXE 1000) frame 5: sp = 0x253FC8C, pc =
0x10006B89
(D:\LITE\LITE.EXE 1000) frame 6: sp = 0x253FE0C, pc =
0x10006B9C
(D:\LITE\LITE.EXE 1000) frame 7: sp = 0x253FE18, pc =
0x401A5E
(D:\LITE\LITE.EXE 1000) frame 8: sp = 0x253FE28, pc =
0x40103A
(D:\LITE\LITE.EXE 1000) frame 9: sp = 0x253FE38, pc =
0xBFF88E93
(D:\LITE\LITE.EXE 1000) frame 10: sp = 0x253FF78, pc =
0xBFF88D41
(D:\LITE\LITE.EXE 1000) frame 11: sp = 0x253FFF4, pc =
0xBFF87759
(D:\LITE\LITE.EXE 1000) frame 12: sp = 0x815A1F54, pc =
0x6
(D:\LITE\LITE.EXE 1000) Exception:
STATUS_ACCESS_VIOLATION
(D:\LITE\LITE.EXE 1000) Error while dumping state
(probably corrupted stack)

Any help in fixing this will be extremely appreciated...


--------------------------------------------------------------
      .---.        .----------    Jonathan George,
     /     \  __  /    ------    Tech. Support, Coder.
    / /     \(  )/    -----     Terra World, Inc.
   //////   ' \/ `   ---       Email: outlaw@terraworld.net
  //// / // :    : ---               -support@terraworld.net
 // /   /  /`    '--                 -root@lite.net
//          //..\\          IRC: net @ irc.lite.net
       ====UU====UU====    Phone: 1-316-332-1616 [office]
           '//||\\`       
            ``''``
  --- mild-mannered programmer by day,                 
      positively grouchy programmer by night           
--------------------------------------------------------------
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1998-07-11  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-11  4:23 Jonathan George [this message]
     [not found] <3.0.5.32.19980711005355.00944100.cygnus.gnu-win32@terraworld.net>
1998-07-11 15:39 ` Christopher G. Faylor
1998-07-13  9:40 Christopher Faylor
1998-07-13  9:40 Fred Reimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3.0.5.32.19980711005355.00944100@terraworld.net \
    --to=outlaw@terraworld.net \
    --cc=gnu-win32@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).