|Subject:||Re: Re: Crash at startup of DDD for Fortran programs|
|Date:||Thu, 18 Dec 2008 14:06:02 +0000|
Thanks for the log, this may help (see later).
No, I cannot reproduce the problem.
What happens if you issue the command "info line main" in gdb?
From your log, the full list of commands send from ddd to gdb is this:
set prompt (gdb)
set height 0
set width 0
set annotate 1
set verbose off
show history filename
show history size
info line main
The last command before the crash is "info line main", so it would be interesting to try that in gdb.
I seem to remember seeing a gdb bug a few years back which was triggered by something like that. Maybe Google will turn up something useful.
I'd like to point out that DDD is maintained by a very small group of volunteers, who do not have access to all possible combinations of hardware and software. This is why its not unusual for a bug to be impossible to replicate on our machines. I have Scientific Linux (i.e. Red Hat), Ubuntu and SuSE; but no Mandriva, hence your DDD and GDB versions are subtly different from mine.
On Thu Dec 18 11:41 , GUEZ Lionel sent:
> On Wed, 2008-12-17 at 14:40 +0100, GUEZ Lionel wrote:
> > Hello. DDD displays an error at startup when I use it on any Fortran
> > program. Here is a test on a two-line program :
> > $ cat plouf.f
> > print *, "plouf"
> > end
> > $ gfortran -g -O0 plouf.f
> > $ ddd a.out
> > The DDD console opens with the following message :
> > "GNU DDD 3.3.11 (i586-mandriva-linux-gnu), by Dorothea LÃtkehaus and
> > Andreas Zeller.
> > Copyright Â 1995-1999 Technische UniversitÃt Braunschweig, Germany.
> > Copyright Â 1999-2001 UniversitÃt Passau, Germany.
> > Copyright Â 2001 UniversitÃt des Saarlandes, Germany.
> > Copyright Â 2001-2004 Free Software Foundation, Inc.
> > Using host libthread_db library "/lib/i686/libthread_db.so.1".
> > (gdb)
> > Segmentation fault"
> > and two dialog boxes appear saying :
> > "GDB terminated abnormally (Segmentation fault)"
> This line says that GDB (the line-oriented debugger underneath DDD)
> terminated abnormally, which it should not do. It may be that DDD has
> told it do do something silly (using too much memory for example), but
> in an ideal world no program should ever crash on any input. You can
> find out what commands have been sent to GDB by examining ~/.ddd/log and
> looking for the lines which begin with "->". If I were you I would try
> debugging your program with gdb directly. By repeating these commands in
> GDB you may be able to replicate the crash, and then you can send a bug
> report to the GDB maintainers.
> Peter Wainwright
> > "/libgfortran/fmain.c: No such file or directory"
> > Does anyone have a suggestion?
> > Sincerely,
> > Lionel GUEZ
Hello. Thank you for your answer. Again, the test Fortran program I am using
has the following two lines:
print *, "plouf"
That is all and that is enough to crash DDD. This Fortran program does not
require much memory!
Please find enclosed the file ".ddd/log" created after the crash. I do not
understand the error messages in that file.
Finally, I have tried running GDB directly on the same program. It works fine:
$ gdb a.out
GNU gdb 6.3-8mdv2007.0 (Mandriva Linux release 2007.0)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-mandriva-linux-gnu"...Using host libthread_db
Starting program: /usr/local/guez/a.out
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xbfffe000
Program exited normally.
So the problem really lies with DDD.
Can you not reproduce the crash with my two-line program?
|[Prev in Thread]||Current Thread||[Next in Thread]|