From: "J. Finch" <finchlady888@hotmail.com>
To: Kai Tietz <kai.tietz@onevision.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
FX <fxcoudert@gmail.com>, GCC Development <gcc@gcc.gnu.org>,
<mingw-w64-public@lists.sourceforge.net>
Subject: RE: internal compiler error: Segmentation fault
Date: Thu, 10 Jan 2008 15:18:00 -0000 [thread overview]
Message-ID: <BAY127-W13DB35CF4D46F039E018788D4A0@phx.gbl> (raw)
In-Reply-To: <OF1D41F31F.131F08F3-ONC12573CC.004FFDD9-C12573CC.005038ED@onevision.de>
>
> This looks fine. What is the call stack looks like? And how does the
> function calling ntdll looks like?
> I think, you should step on an "int 3". Because you simply debug the
> exception handling routine itself.
>
Hi, Kai:
I attach the stack in the following:
C:\temp\fortran>cdb gfortran -O1 c.f90
Microsoft (R) Windows Debugger Version 6.8.0004.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
CommandLine: gfortran -O1 c.f90
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 00000000`00400000 00000000`0043c000 image00000000`00400000
ModLoad: 00000000`77ec0000 00000000`77ff9000 ntdll.dll
ModLoad: 00000000`77d40000 00000000`77eb3000 C:\WINDOWS\system32\kernel32.dll
ModLoad: 000007ff`7fc00000 000007ff`7fc86000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 00000000`77c20000 00000000`77d2c000 C:\WINDOWS\system32\USER32.dll
ModLoad: 000007ff`7fc90000 000007ff`7fd2c000 C:\WINDOWS\system32\GDI32.dll
(a20.a24): Break instruction exception - code 80000003 (first chance)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
00000000`77ef2aa0 cc int 3
0:000> g
ModLoad: 000007ff`7d500000 000007ff`7d539000 C:\WINDOWS\system32\IMM32.DLL
ModLoad: 000007ff`7fee0000 000007ff`7ffe5000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 000007ff`7fd30000 000007ff`7fec9000 C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 000007ff`7e9c0000 000007ff`7e9e2000 C:\WINDOWS\system32\Secur32.dll
ModLoad: 000007ff`69300000 000007ff`6930d000 C:\WINDOWS\system32\LPK.DLL
ModLoad: 000007ff`78e80000 000007ff`78f0e000 C:\WINDOWS\system32\USP10.dll
c.f90: In function 'MAIN__':
c.f90:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
ntdll!ZwTerminateProcess+0xa:
00000000`77ef0caa c3 ret
0:000> kb
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\kernel32.dll -
RetAddr : Args to Child
: Call Site
00000000`77d5a329 : 00000000`00000001 00000000`00000001 00000000`00000001 00000000`00000000 : ntdll!ZwTerminateProcess+0xa
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\msvcrt.dll -
000007ff`7fc4069b : 00000000`00000000 00000000`00428030 00000000`00000000 00000000`40000060 : kernel32!ExitProcess+0x59
000007ff`7fc40863 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvcrt!strerror+0x3beb
*** ERROR: Module load completed but symbols could not be loaded for image00000000`00400000
00000000`0040141d : 00000000`00000003 00000000`003d3590 00000000`00000000 00000000`00419a10 : msvcrt!initterm+0x193
00000000`00000003 : 00000000`003d3590 00000000`00000000 00000000`00419a10 00000000`00000000 : image00000000_00400000+0x141d
00000000`003d3590 : 00000000`00000000 00000000`00419a10 00000000`00000000 00000000`00000000 : 0x3
00000000`00000000 : 00000000`00419a10 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3d3590
00000000`00419a10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : image00000000_00400000+0x19a10
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
0:000>
_________________________________________________________________
Share life as it happens with the new Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008
next prev parent reply other threads:[~2008-01-10 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY127-W3905CADAD6C9E6370134AD8D4A0@phx.gbl>
2008-01-10 14:36 ` Kai Tietz
2008-01-10 15:18 ` J. Finch [this message]
2008-01-10 15:32 ` J. Finch
2008-01-10 16:06 ` Kai Tietz
2008-01-10 18:38 ` J. Finch
[not found] <19c433eb0801090519l676a7645u162dc18760e99cc9@mail.gmail.com>
[not found] ` <BAY127-W419B706D2D2ACAC13608CE8D490@phx.gbl>
2008-01-09 15:09 ` FX
2008-01-09 15:37 ` Kai Tietz
2008-01-09 15:43 ` FX
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=BAY127-W13DB35CF4D46F039E018788D4A0@phx.gbl \
--to=finchlady888@hotmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=kai.tietz@onevision.com \
--cc=mingw-w64-public@lists.sourceforge.net \
/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).