Before upgrading to libc 2.8.90, I wasn't getting any warnings about the
dlopen call. Now each of them results in a valgrind warning about an
invalid read. I'd actually forgotten about making that post.
--- On Mon, 9/8/08, Matthias Klose <[EMAIL PROTECTED]> wrote:
From: Matthias Klose <[EMAIL PROTECTED]>
Subject: [Bug 238469] Re: valgrind reports errors in libc 2.8.90
To: [EMAIL PROTECTED]
Date: Monday, September 8, 2008, 5:18 PM
so what is the bug?
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
valgrind reports errors in libc 2.8.90
https://bugs.launchpad.net/bugs/238469
You received this bug notification because you are a direct subscriber
of the bug.
Status in “glibc” source package in Ubuntu: Incomplete
Bug description:
I originally noticed these while running valgrind on a Qt app. However,
i've noticed that the errors can be found running even the simplest
programs.
The program
---
int main(int argc, char **argv)
{
return 1;
}
---
Attached is the output of 'valgrind --leak-check=full' on said program.
Ubuntu version : 8.04
--
valgrind reports errors in libc 2.8.90
https://bugs.launchpad.net/bugs/238469
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
