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

List:       kde-bugs-dist
Subject:    [Bug 79362] Debug info is lost for .so files when they are dlclose'd
From:       Kevin Fitch <kfitch42 () gmail ! com>
Date:       2011-02-28 16:42:08
Message-ID: 20110228164208.EE7238050D () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=79362





--- Comment #25 from Kevin Fitch <kfitch42 gmail com>  2011-02-28 17:42:05 ---
OOOOoooohhhh. I totally misunderstood where you were going in the previous
post. This seems to get the job done with very little new code. Unfortunately I
suspect it has some nasty side effects. In particular, there are some places
that print out stacktraces without going through pp_ExeContext. So those would
end up using a stale value in VG_(ec_curr_ecu).

Also, is it a true statement that only 1 thread is ever printing stack traces
at a time? I don't have a good feel for all the guarantees of valgrind yet. The
case I am thinking about is two threads doing something bad (e.g. accessing off
the end of a malloc'ed array) at the same time. They would both print a current
stack trace (i.e. where the bad access happened) and a past stack trace (i.e.
where the allocation of said array occurred).

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]