Your message dated Tue, 13 Dec 2016 00:32:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#760978: gdb crash
has caused the Debian Bug report #760978,
regarding [gdb] gdb segfaults when reading symbols
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
760978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760978
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdb
Version: 7.7.1-2
Severity: normal
--- Please enter the report below this line. ---
Dear maintainer,
I encountered the following segmentation fault of GDB when debugging my
program:
$ gdb ./explicit_tree_aut_test
GNU gdb (Debian 7.7.1-2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./explicit_tree_aut_test...zsh: segmentation fault gdb
./explicit_tree_aut_test
I can reproduce it on my (debian sid) machine by the following sequence
of operations (provided adequate supporting packages are installed):
$ git clone https://github.com/ondrik/libvata.git libvata-gdbbug (1)
$ cd libvata-gdbbug (2)
$ make debug (3)
$ cd build/unit_tests (4)
$ gdb ./explicit_tree_aut_test (5)
Note that when I run "make release" instead of "make debug" in step (3),
then gdb works fine (without debuggin symbols, of course, but does not
SEGFAULTs). Under bash, the results is the same as under zsh.
Can I ask you about any idea how to make GDB work again? Thank you.
Best regards,
Ondra
--- System information. ---
Architecture: amd64
Kernel: Linux 3.14-1-amd64
Debian Release: jessie/sid
500 unstable merlin.fit.vutbr.cz
500 unstable debian.yeasoft.net
--- Package information. ---
Depends (Version) | Installed
=========================================-+-=========================
libc6 (>= 2.15) |
libexpat1 (>= 2.0.1) |
liblzma5 (>= 5.1.1alpha+20110809) |
libncurses5 (>= 5.5-5~) |
libpython2.7 (>= 2.7) |
libreadline6 (>= 6.0) |
libtinfo5 |
zlib1g (>= 1:1.2.0) |
Recommends (Version) | Installed
=========================-+-===========
libc-dbg |
gdbserver | 7.7.1-2
Suggests (Version) | Installed
=======================-+-===========
gdb-doc |
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Tue, Jul 12, 2016 at 09:14:58AM +0200, Christoph Mathys wrote:
> I recently triggered a crash with an endless recursion in cp-demangle.
> I think it is this bug:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=16957
>
> I compiled a backport from gdb 7.11 and could no longer reproduce the
> error. We could try and backport the patch to gdb 7.7. I'd be willing
> to give it a try if there is a chance for inclusion.
Thanks for the offer, we are close to Stretch release and we also have a
backport available, I do not think it is worth any effort on patching stable.
Regards
--
Hector Oron
signature.asc
Description: PGP signature
--- End Message ---
