[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 113642] valgrind crashes when trying to read debug information
From:       Julian Seward <jseward () acm ! org>
Date:       2005-10-04 15:30:40
Message-ID: 20051004153040.9273.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=113642         




------- Additional Comments From jseward acm org  2005-10-04 17:30 -------
> ?  And maybe add in (debug_info_sz > 4), and possibly check that debug_str
> and debug_abbv are non-NULL.


Or perhaps .. for dealing with potentially explosive pointers like
this, we could inquire with aspacem whether it's safe to dereference
(perhaps by checking that the pointer points into the same
segment that the .so has been transiently mmaped into).  It's
two calls to VG_(am_find_nsegment), but that's not catastrophically
expensive since it's a binary search now.
[prev in list] [next in list] [prev in thread] [next in thread]