This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
symtab/1508: hpread.c does not set debug format
- From: mec dot gnu at mindspring dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 13 Jan 2004 06:34:15 -0000
- Subject: symtab/1508: hpread.c does not set debug format
- Reply-to: mec dot gnu at mindspring dot com
>Number: 1508
>Category: symtab
>Synopsis: hpread.c does not set debug format
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jan 13 06:38:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: mec.gnu@mindspring.com
>Release: gdb HEAD 2004-01-13 02:58:01 UTC
>Organization:
>Environment:
target=native, host=hppa2.0w-hp-hpux11.11, osversion=vanilla
gdb=HEAD 2004-01-13 02:58:01 UTC
cc=hpansic-B.11.11.28707.GP
as=vendor, ld=vendor, libc=vendor
gformat=-g
>Description:
info source does not know the debug format:
(gdb) info source
Current source file is /house/chastain/gdb/s1/gdb/testsuite/gdb.base/sepdebug.c
Located in /house/chastain/gdb/s1/gdb/testsuite/gdb.base/sepdebug.c
Contains 150 lines.
Source language is c.
Compiled with unknown debugging format.
Does not include preprocessor macro info.
hpread.c has code to call record_debugformat, but the code does not get executed.
This also happens with gdb 5.3 (gdb 6.0 does not build on this configuration), so it is not a regression.
>How-To-Repeat:
Run the gdb test suite and look for "info source" lines in gdb.log. Any script that calls get_debug_format, such as sepdebug.exp, is a good candidate.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: