[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#483202: marked as done (gfortran: gdb sees debugging symbols depending on source filename)

Your message dated Wed, 15 Feb 2012 17:52:08 +0100
with message-id <20120215165208.GA20488@physik.fu-berlin.de>
and subject line Re: gfortran: Suggestion for -M flag
has caused the Debian Bug report #483202,
regarding gfortran: gdb sees debugging symbols depending on source filename
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
483202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483202
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Subject: gfortran: gdb sees debugging symbols depending on source filename
Package: gfortran
Version: 4:4.1.1-15
Severity: minor

*** Please type your report below this line ***
Depending on how the Fortran source files are named, gdb may or may not find the debugging symbols when doing a "list".
Example:

jbatista@localhost:~$ cat teste.f
        program teste
        stop
        end program
jbatista@localhost:~$ gfortran -g teste.f -o teste
jbatista@localhost:~$ gdb teste
GNU gdb 6.4.90-debian
Copyright (C) 2006 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 "x86_64-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) list
1       ../sysdeps/x86_64/elf/start.S: Arquivo ou diretório não encontrado.
        in ../sysdeps/x86_64/elf/start.S
(gdb) quit
jbatista@localhost:~$ mv teste.f teste.f90
jbatista@localhost:~$ gfortran -g teste.f90 -o teste
jbatista@localhost:~$ gdb teste
GNU gdb 6.4.90-debian
Copyright (C) 2006 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 "x86_64-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) list
1               program teste
2               stop
3               end program
(gdb) quit
jbatista@localhost:~$


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (800, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-3-amd64
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)

Versions of packages gfortran depends on:
ii  cpp                           4:4.1.1-15     The GNU C preprocessor (cpp)
ii  gcc                           4:4.1.1-15     The GNU C compiler
ii  gfortran-4.1                  4.1.1-21       The GNU Fortran 95 compiler
ii  gdb                           6.4.90.dfsg-1  The GNU Debugger

gfortran recommends no packages.

-- no debconf information

_________________________________________________________________
Receba GRÁTIS as mensagens do Messenger no seu celular quando você estiver offline. Conheça  o MSN Mobile!
http://mobile.live.com/signup/signup2.aspx?lc=pt-br

--- End Message ---
--- Begin Message --- 
Version: 4.6.0-2

I believe that the issue has been fixed upstream in GCC 4.6.0.

>From http://gcc.gnu.org/gcc-4.6/changes.html:
"Support the generation of Makefile dependencies via the -M...
 flags of GCC; you may need to specify the -cpp option in addition.
 The dependencies take modules, Fortran's include, and CPP's #include
 into account. Note: Using -M for the module path is no longer
 supported, use -J instead."

--- End Message ---
Reply to: