Package: gdb
Version: 6.8.50.20090116.python-1
Severity: important
Tags: fixed-upstream
Hello,
gdb crashed when I tried to run a program with breakpoint in
someclass::operator(). Debugging has shown the problem was that the parser
of C++ names in gdb mishandled operator(), and further ignored the error.
The error was fixed in the upstream cvs on 31th March. Please, consider
updating the package.
Regards
Jiri Palecek
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.27-test-pcw (SMP w/1 CPU core; PREEMPT)
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdb depends on:
ii libc6 2.9-12 GNU C Library: Shared
libraries
ii libexpat1 1.95.8-3.4 XML parsing C library -
runtime li
ii libncurses5 5.7+20090124-1 shared libraries for terminal
hand
ii libreadline5 5.2-3 GNU readline and history
libraries
ii python2.5 2.5.4-1 An interactive high-level
object-o
ii zlib1g 1:1.2.3.3.dfsg-3 compression library - runtime
gdb recommends no packages.
Versions of packages gdb suggests:
ii gdb-doc 6.7.1-1 The GNU Debugger Documentation
-- no debconf information
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org