** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
valgrind on amd64 no longer works with 32-bit binaries
To manage notifications about this bug go to:
https
This should be fixed upstream.
https://bugs.kde.org/show_bug.cgi?id=286270
Can the maintainer please update the package?
** Bug watch added: KDE Bug Tracking System #286270
https://bugs.kde.org/show_bug.cgi?id=286270
--
You received this bug notification because you are a member of Ubuntu
Bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: valgrind (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
va
Right, so this seems to be working fine for >= precise by installing the
multiarch libc6-dbg. Marking the eglibc task done, but opening one for
valgrind to perhaps improve the error message to suggest this.
** Also affects: valgrind (Ubuntu)
Importance: Undecided
Status: New
** Changed
I can also confirm that sudo apt-get install libc6-dbg:i386 fixed the
problem on Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
valgrind on amd64 no longer works with 32-bi
As a followup, installing libc6-dbg:i386 on Ubuntu 12.04 works without
complaint, and solves this problem.
--ryan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
valgrind on amd64 no
Also having this issue. I can't debug my LuaJIT program with this issue,
as LuaJIT's custom allocator is mandatory on x64 and Valgrind doesn't
track all errors when using it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Same problem here. I got the valgrind working with some real stupid hack
but not sure what it breaks. Here are the steps:
1. Move from /usr/lib/debug/ the following directories to the following places:
usr/bin/ -> usr/bintmp/
usr/lib/ -> usr/libtmp/
usr/sbin/ -> usr/sbintmp/
sbin/ -> s
Same problem here.
valgrind-3.6.1-Debian
Ubuntu 11.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
valgrind on amd64 no longer works with 32-bit binaries
To manage notifications abo
I have exactly the same issue. Is that fixed in some dev package to
test?
Thanks,
Daniele.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
valgrind on amd64 no longer works with 32-bit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: eglibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
valg
Hello,
I had a very similar problem as descripted above (running valgrind 32-bit on
ubuntu 11.10 with 64-bit-arch).
Unpacking to /usr/lib/debug/lib/i386-linux-gnu as descriped above worked for me.
Thank you a lot!!
Greetings,
Claudio
--
You received this bug notification because you are a me
Oh wow, sorry for the thinko, I actually typed gcc -m64 machinally
instead of -m32; indeed I can reproduce your issue with Ubuntu precise /
12.04 and -m32.
I also confirmed that the initial idea of installing libc6-dbg:i386 was
the right one, albeit it has conflicts.
After unpacking /usr/lib/debu
Quick follow up:
My initial comments said I was on a 11.04 system, which is incorrect;
this is happening on 11.10, as the bug metadata correctly states.
I just tested this on Ubuntu 10.10 and Ubuntu 11.04, and both versions
have a valgrind that works with 32-bit binaries on a 64-bit system, so
th
> Works for me with 1:3.6.1-6ubuntu1 from Ubuntu precise:
> gcc -m64 -o hello hello.c
Yes, that would work, as you tested a 64-bit binary. The problem is that
valgrind doesn't work with 32-bit binaries on a 64-bit system. Use -m32
instead of -m64 and see if it changes anything.
(You'll need to ap
Works for me with 1:3.6.1-6ubuntu1 from Ubuntu precise:
gcc -m64 -o hello hello.c
valgrind ./hello
==20954== Memcheck, a memory error detector
==20954== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==20954== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==2095
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881236
Title:
valgrind on amd64 no longer works with 32-bit binaries
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
17 matches
Mail list logo
