Your message dated Tue, 5 Sep 2006 21:20:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#239503: cscope: Doesn't recognize function defs with
arrays as arguments
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: cscope
Version: 15.4-2
Severity: normal
With this file in a directory by itself:
----- foo.cc -----
void foo( int a[42] )
{
int b;
}
------------------
Running cscope foo.cc
and looking up the C symbol b produces this output:
0 foo.cc <global> 3 int b;
It should be foo not <global>. If the function definition is
void foo( int a )
there's no problem, the output is:
0 foo.cc foo 3 int b;
-- System Information:
Debian Release: 3.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-ck1
Locale: LANG=C, LC_CTYPE=C
Versions of packages cscope depends on:
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libncurses5 5.4-2 Shared libraries for terminal hand
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2006-09-05 at 19:59:56 +0200, Peter Cordes <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 05, 2006 at 01:18:02PM +0200, Tobias Klauser wrote:
> > On 2006-09-05 at 08:53:41 +0200, Peter Cordes <[EMAIL PROTECTED]> wrote:
> > > On Sun, Sep 03, 2006 at 02:16:58PM +0200, Tobias Klauser wrote:
> > > > Can you still reproduce this bug with a recent version of cscope?
> > > >
> > > > I tried to reproduce the with the procedure you mentioned above using
> > > > cscope-15.5+cvs20060902-1 but the bug you described did not show up.
> > >
> > > I tried it again myself, and it does appear to be fixed in the latest
> > > version. It was still present in version 15.5+cvs20050816-2.
>
> > Version 15.5+cvs20060902-1 is in unstable now. Could you try to
> > reproduce it there and check wheter the bug is really fixed
>
> The bug is not present in 15.5+cvs20060902-1. I tried to say that in my
> last message, but I could have been more explicit. Anyway, it looks like
> the bug is fixed.
Thanks, I just wanted to make sure. ;-)
> > (I just tried to reproduce the steps you described in the bug report).
>
> I don't remember what I was working on when I first reported the bug, so
> that's all I did myself yesterday. I tried it before and after upgrading to
> 15.5+cvs20060902-1, and saw the difference, so that's a pretty good sign
> that it's fixed.
OK, closing the bug report now as it is confirmed as fixed in
15.5+cvs20060902-1.
Cheers, Tobias
--- End Message ---
