This bug was fixed in the package valgrind - 1:3.7.0-0ubuntu3.1
---
valgrind (1:3.7.0-0ubuntu3.1) precise-proposed; urgency=low
* fix-buffer-overflows.patch: fix overflows in vgdb
* 05_fix-callgrind_control.patch: fix valgrind process name (LP: #1036283)
* fix-VEX-PCMPxSTRx.patc
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable na
** Branch linked: lp:ubuntu/precise-proposed/valgrind
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
To manage no
Nevermind, I see this bug was later expanded to also include several
buffer overflows, so the quote of fix-buffer-overflows.patch was in the
right place.
I've just downloaded the .deb of Valgrind 1:3.7.0-0ubuntu3.1 and
installed it manually, and the problem I originally reported (callgrind
looking
Thanks for releasing the patch Steve. By the way, I think you've quoted
the wrong patch in this bug (fix-buffer-overflows.patch instead of
05_fix-callgrind_control.patch) but the right patch is in the version
anyway. As soon as it's in -proposed I'll test it and give you a quick
reply.
--
You rec
valgrind-3.7.0/debian/patches/fix-buffer-overflows.patch says:
Description: fix a couple of overflows in vgdb
the overflows cause vgdb to crash in quantal with gcc-4.7
the crash does not occur on my precise platform but fix the issue
there just to be safe.
I'm allowing this in the SRU in t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: valgrind (Ubuntu Precise)
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/1036283
Ti
** Also affects: valgrind (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of differ
** Description changed:
- When starting a Callgrind session using "valgrind", the actual
- executable name is "valgrind.bin". However, when callgrind_control
- searches for processes, its Perl regexp does not allow for this
- possibility. See callgrind_control line 32:
+ [Impact]
+ When starting a
precise sru is going to be tracked in bug 1027977
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
To manage notifi
This bug was fixed in the package valgrind - 1:3.7.0-0ubuntu4
---
valgrind (1:3.7.0-0ubuntu4) quantal; urgency=low
* fix-buffer-overflows.patch: fix overflows in vgdb
* 05_fix-callgrind_control.patch: fix valgrind process name (LP: #1036283)
* fix-VEX-PCMPxSTRx.patch: fix strstr
** Branch linked: lp:~jtaylor/ubuntu/quantal/valgrind/various-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
Can someone please push that patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
To manage notifications about
thanks for the fix in bug description - works !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
To manage notifica
Is it very hard to apply this patch? It's hard to believe that nobody
uses valgrind tools family under Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot c
Same problem on 12.04 release. Please fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
To manage notifications
Changing the line 32 as proposed solves the problem. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
To
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/1036283
Title:
c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036283
Title:
callgrind_control cannot connect because of different executable name
To manage notifications about this bug go to:
https://bugs.launchpa
19 matches
Mail list logo
