fdb internal error

[space]

Hello,

I am trying to debug an application with fdb but the compiler crashes whenever I attempt to run the code. This is LF6.2 on Linux.

I start the debugger:

> fdb <executable>

Then set the breakpoint:
fdb* break MAIN__

After that, either of the following fails
fdb* Run
fdb* run "< in000"

with this message:

The program: ../bin/enlil.m1m.125x50x30 < in000 starting.
Internal error: (change_mode, exec 1, prev 0, file:run_process.c line:1134) !

What is happening? I cannot figure out what am I doing wrong.

Thank you for any comments,

Jan

[Lahey Support]

Sorry but not enough information has been supplied to determine the cause. But, it doesn't look like you are doing anything wrong.

Please test the compiler and debugger using demo.f90 included with the compiler. If you can debug demo.f90, provide a simple/reduced example that can be used to reproduce the problem. Include compile and debug commands used to reproduce the problem.

[mcscythie]

Sorry but not enough information has been supplied to determine the cause. But, it doesn't look like you are doing anything wrong.

Please test the compiler and debugger using demo.f90 included with the compiler. If you can debug demo.f90, provide a simple/reduced example that can be used to reproduce the problem. Inlclude compile and debug commands used to reproduce the problem.


I have run across this same error while using fdb on both Fedora Core 4 and Gentoo 2005.1 systems with lf9561 express update e. I compiled demo.f90 and it too showed me the error:

tmp $ fdb ./demo_lahey
FDB [Fujitsu Debugger for C/C++ and Fortran] Version 1.01(libc6)
Please wait to analyze the DEBUG information.
fdb* run
The program: ./demo_lahey starting.
Internal error: (change_mode, exec 1, prev 0, file:run_process.c line:1138) !
fdb*

Thank you

[dhunt]

Hi all:

This problem appears for us, too:

$ uname -a
Linux jay 2.6.12-1.1381_FC3smp #1 SMP Fri Oct 21 04:03:26 EDT 2005 i686 i686 i386 GNU/Linux

$ cat foo.f
program foo
print *, 'foo!'
end
$ lf95 -g -o foo foo.f
Encountered 0 errors, 0 warnings in file foo.f.
$ fdb foo
FDB [Fujitsu Debugger for C/C++ and Fortran] Version 5.0.7(libc6.5)
Please wait to analyze the DEBUG information.
fdb* run
The program: foo starting.
Internal error: (change_mode, exec 1, prev 0, file:run_process.c line:1134) !
fdb*

The inability to use 'fbd' causes us a major problem. Any help or suggestions appreciated!

Regards,

Doug Hunt

[Lahey Support]

LF95 Linux v6.1 is not compatible with current releases of Linux.

To be compatible with current Linux distributions/releases you'll need to upgrade to the current release of LF95 for Linux.

LF95 Linux is not officially supported on 64 bit operating systems. See http://www.laheyforum.com/showthread.php?t=10440&highlight=bit

[dhunt]

Hi: I am using version 6.2, not 6.1. The change on our end seems to be moving
from Fedora core 2 (kernel 2.4) to Fedora Core 3 (kernel 2.6). This is all on 32 bit Intel
machines:

[dhunt@jay ~]$ uname -a
Linux jay 2.6.12-1.1381_FC3smp #1 SMP Fri Oct 21 04:03:26 EDT 2005 i686 i686 i386 GNU/Linux

[dhunt@jay ~]$ fdb -V
fdb: Fujitsu Debugger for C/C++ and Fortran Version 5.0.7(libc6.5)
fdb: (Jan 7 2003 16:49:06 - Linux 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686)


Regards,

Doug Hunt

[dhunt]

Hi all: We just ran some more tests on the fdb failure.

On Fedora Core 3, Intel 32 bit (i686) with a downgraded kernel:

[dhunt@pegasus ~]$ uname -a
Linux pegasus.cosmic.ucar.edu 2.6.9-1.667 #1 Tue Nov 2 14:41:25 EST 2004 i686 i686 i386 GNU/Linux

fdb works:
[dhunt@pegasus ~]$ cat foo.f
program foo
print *, 'hi!'
end
[dhunt@pegasus ~]$ fdb a.out
FDB [Fujitsu Debugger for C/C++ and Fortran] Version 5.0.7(libc6.5)
Please wait to analyze the DEBUG information.
fdb* run
The program: a.out starting.
hi!
The program: a.out terminated.

But with a more recent kernel (2.6.12) and with the most recent kernel straight from kernel.org (2.6.15) fdb fails as described earlier, with this message:

Internal error: (change_mode, exec 1, prev 0, file:run_process.c line:1134) !

Please help! This is a show-stopper for us. We are expecting our weather satellite to be
lanuched in two weeks and we need to be able to debug our code when that happens. If we cannot get lf95 and debugger working, we will change to a different compiler and you will lose much potential future business.

This is probably a simple problem, but one that can only be solved with the source code to fdb.

Thanks in advance,

Doug Hunt

[Lahey Support]

Disable SeLinux and Copy /usr/local/lf9562/bin/fdb_libc65 to /usr/local/lf9562/bin/fdb_libc6.

Let us know if this resolves the FDB problem.


>$ uname -a
Linux localhost.localdomain 2.6.11-1.1369_FC4 #1 Thu Jun 2 22:55:56 EDT 2005 i686 athlon i386 GNU/Linux

>$ ls -l /lib/libc.so.6
lrwxrwxrwx 1 root root 13 Apr 4 2006 /lib/libc.so.6 -> libc-2.3.5.so

[germ_e_1]

I installed the demo lf95 compiler and all worked fine but when I purchased LF95 Express and re-installed, this ugly "internal error" reared its ugly head. I am running stock ubuntu 6.06 LTS ("dapper") with uname reporting

Linux ubuntu 2.6.15-23-686 #1 SMP PREEMPT . . .

The bad part is that the DEMO sucked me in, it worked great . . .