This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
debug/1621: Debugging with complex numbers
- To: gcc-gnats at gcc dot gnu dot org
- Subject: debug/1621: Debugging with complex numbers
- From: Joseph Myers <jsm28 at cam dot ac dot uk>
- Date: Thu, 11 Jan 2001 19:04:27 +0000
- Cc: jsm28 at cam dot ac dot uk
>Number: 1621
>Category: debug
>Synopsis: Debugging with complex numbers
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jan 11 11:06:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 2.97 20010110 (experimental)
>Organization:
none
>Environment:
System: Linux decomino 2.2.18 #1 Sun Jan 7 21:04:55 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:
Debugging with complex numbers is fairly broken. Some coordination
with GDB may be needed.
>How-To-Repeat:
See <URL:http://gcc.gnu.org/ml/gcc/2000-12/msg00536.html>.
>Fix:
At the very least, GCC should not make claims about future versions of
GDB and leave such claims in the manual for years without some
coordination to make the claims become true. Properly, full support
for debugging with complex numbers should be coordinated with GDB -
GCC should emit correct stabs/DWARF-2 information, and document the
required GDB version, and GDB should understand the information.
>Release-Note:
>Audit-Trail:
>Unformatted: