[Bug binutils/11302] Segfault in _bfd_dwarf2_find_nearest_line

2010-03-03 Thread amodra at gmail dot com
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2010-03-04 04:02 --- Subject: Bug 11302 CVSROOT:/cvs/src Module name:src Changes by: amo...@sourceware.org 2010-03-04 04:01:53 Modified files: bfd: ChangeLog dwarf2.c Log message:

[Bug binutils/11302] Segfault in _bfd_dwarf2_find_nearest_line

2010-03-03 Thread amodra at gmail dot com
--- Additional Comments From amodra at gmail dot com 2010-03-04 00:15 --- Huh, there's lots of sloppy programming in dwarf2.c I'm testing a patch that catches all alloc failures in that file. -- What|Removed |Added ---

[Bug binutils/11302] Segfault in _bfd_dwarf2_find_nearest_line

2010-03-03 Thread loose at astron dot nl
--- Additional Comments From loose at astron dot nl 2010-03-03 16:10 --- Created an attachment (id=4642) --> (http://sourceware.org/bugzilla/attachment.cgi?id=4642&action=view) Partial patch fixes most (or all?) segfaults Here's a minimal patch that fixes most segfaults. I.e., I have n

[Bug binutils/11302] Segfault in _bfd_dwarf2_find_nearest_line

2010-03-03 Thread loose at astron dot nl
--- Additional Comments From loose at astron dot nl 2010-03-03 11:26 --- Hi Nick, Segfaults remain, though they occur at different places now. Again, they have to do with not checking the return value of bfd_zalloc. This still happens in a LOT of places. Is this a deliberate choice of s

[Bug binutils/11302] Segfault in _bfd_dwarf2_find_nearest_line

2010-02-25 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2010-02-25 12:11 --- Hi Marcel, > I encountered several different, but reproducible, segfaults in > _bfd_dwarf2_find_nearest_line() in bfd/dwarf2.c. Currently, I'm using > binutils-2.19.51, but I've seen this happening with 2.16, and