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

List:       kde-bugs-dist
Subject:    [Bug 253519] Memcheck reports auxv pointer accesses as invalid reads.
From:       Julian Seward <jseward () acm ! org>
Date:       2010-10-07 16:43:21
Message-ID: 20101007164321.93246726BB () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #4 from Julian Seward <jseward acm org>  2010-10-07 18:43:20 ---
(In reply to comment #1)
> I'm not sure why you're accessing auxv like that though - the usual way to
> access it is just to search up the stack past the environment data as shown
> here:

That's all very well if you're a complete executable, and you have
some way to figure out where the frame for main() is, so you can work
upwards from that.  But what if you're just a library and you want to
find out?  That's the use case that Jacob is referring to, plus there
is another such case somewhere in Firefox -- one of the innumerable
graphics libraries needs to figure out whether Neon is supported.

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