[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:       Tom Hughes <tom () compton ! nu>
Date:       2005-10-04 15:34:34
Message-ID: 20051004153434.10353.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 tom compton nu  2005-10-04 17:34 -------
In message <20051004153039.9255.qmail ktown kde org>
        Julian Seward <jseward acm org> wrote:

> 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.


Well the address should be part of memory that we have just mmaped so
it shouldn't really be bogus...

The problem here is that there was no such section in the file so the
default value of zero is still in the variable.

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