Hi, Kai,
This is what you want, with -dH. If you need further information, please let me
know. Finch.
.
.
(8b8.8bc): Break instruction exception - code 8003 (first chance)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntdll.dll -
ntdll!DbgB
Hi,
"J. Finch" wrote on 10.01.2008 16:31:38:
Thank you very much for your dumps, but you should use on runtime the
option '-dH' option to enforce that you reach the point, where the
exception is caused.
> stack before and after segmentation fault is as:
>
>
> ..
> ..
> ntdll!KiUserAp
Hi,
stack before and after segmentation fault is as:
..
..
ntdll!KiUserApcDispatcher+0x15:
`77ef30a5 488bcc mov rcx,rsp
0:000> p
ntdll!KiUserApcDispatcher+0x18:
`77ef30a8 b201mov dl,1
0:000> k
Child-SP RetAddr Call Site
0
>
> 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 gfo
Hi,
"J. Finch" wrote on 10.01.2008 15:23:56:
>
> on the issue as stated in the subject regarding x86_64-pc-mingw64, I
> have downloaded MS debugger as suggested by FX, and I attach the
> logs where command "p" is stepping.
>
> fortran Program, c.f90, for test, one statement only
> [program beg
> To have a better chance to find the issue could you anwser these question?
I'll let J. answer these himself, since I have no direct experience of
the bug myself (no Win64 machine), but...
> a) Does this happens on a cross compiler, too?
I doubt it, since he sees the bug even on trivial program
> [for [EMAIL PROTECTED] and [EMAIL PROTECTED] readers, seeshort thread
> starting at http://gcc.gnu.org/ml/fortran/2008-01/msg00103.html]
>
> > Gcc gets the similar problem. It only works without optimization.
> It seems not a problem with gfortran.
>
> OK, then it'd be more appropriate to ask
[for [EMAIL PROTECTED] and [EMAIL PROTECTED] readers, seeshort thread
starting at http://gcc.gnu.org/ml/fortran/2008-01/msg00103.html]
> Gcc gets the similar problem. It only works without optimization. It seems
> not a problem with gfortran.
OK, then it'd be more appropriate to ask the mingw m
