[Debian #194969] gperf: wrong file and line numbers in warning/error messages

[J.H.M. Dassen (Ray)]

The following was reported as a bug through the Debian bug tracking system
(http://bugs.debian.org); please Cc: address@hidden on on-topic
responses.

From: Rob Leslie <address@hidden>
Date: Tue, 27 May 2003 16:24:25 -0700

Package: gperf
Version: 3.0-1
Severity: normal
Tags: sid upstream

Although the new version of gperf tries to be helpful by inserting #line
directives in the output to reflect the actual input source lines of keywords,
etc., it fails to reset this to reflect portions of the output which are
generated by gperf. Thus in cases when gperf generates invalid code, the file
and line numbers reported by the compiler are wrong.

For example:

frametype.gperf:326: warning: useless keyword or type name in empty declaration

when the actual error is in frametype.c:357, but #line was reset as follows
on frametype.c line 31:

#line 1 "frametype.gperf"

(followed by legitimate output from frametype.gperf, but #line is not reset
after this output.)


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux phobos 2.4.20-3-686-smp #1 SMP Sun May 18 21:32:16 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages gperf depends on:
ii  libc6                         2.3.1-17   GNU C Library: Shared libraries an
ii  libgcc1                       1:3.3-2    GCC support library
ii  libstdc++5                    1:3.3-2    The GNU Standard C++ Library v3

-- no debconf information
-- 
I think the most important thing about Linux is that it gives people the
ability to do what they want.
        Alan Cox in http://www2.linuxjournal.com/articles/culture/012.html