How to debug "Access not within mapped region" runtime error

[Florian]

Jerry DeLisle wrote:
> Florian wrote:
>> Florian wrote:
>>> Jerry DeLisle wrote:
>>>> Florian wrote:
>>>>>
>>>>> I have a piece of code causing runtime troubles with gfortran 
>>>>> (compiling problems are solved thanks to your quick patchings). It 
>>>>> works with NAG, lahey, and intel fortran compiler, so I guess the 
>>>>> troubles are related with gfortran, that's why I would ask for 
>>>>> advice here how to debug the situation.
>>>>>
>>
>>
>> I could reduce my test case a lot now to show where the gdb seg fault 
>> comes from. I believe that this might be also the solution to the 
>> actual problem, though I am not sure yet.
>>
>> This produces a seg fault in gdb when setting a breakpoint to 
>> chartestmod.f90:5 and trying to print startdate:
>>
>>
> ... SNIP ...
> 
>>
>>
>> Now, change in chartestmod.f90 'LEN=*' to 'LEN=19' and gdb does not 
>> segfault anymore. I somehow think that this is related to my actual 
>> problem, so: any ideas if this is related to a gfortran bug?
>>
> 
> I can not reproduce the problem.  What operating system are you using 
> and what hardware platform?.

debian lenny (testing), 2.6.21-2-686

GNU gdb 6.4.90-debian

> 
> Can you send the complete result of 'gfortran -v' output.  This will 
> give us some configuration and build information.
> 

gfortran -v
Using built-in specs.
Target: i386-pc-linux-gnu
Configured with: /home/fx/gfortran_nightbuild/trunk/configure 
--prefix=/home/fx/gfortran_nightbuild/irun-20070808 
--enable-languages=c,fortran --build=i386-pc-linux-gnu 
--enable-checking=release --with-gmp=/home/fx/gfortran_nightbuild/software
Thread model: posix
gcc version 4.3.0 20070808 (experimental)





thanks florian