Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2014-08-23 Thread Samuel Bronson
Simon McVittie writes: > In the Debian package, the instrumentation is only present in the "debug > build" (install dbus-1-dbg and add > /usr/lib/x86_64-linux-gnu/dbus-1.0/debug-build/lib to the > LD_LIBRARY_PATH), not in the build that is normally used by the OS. Huh, why isn't the valgrind stu

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2014-06-25 Thread Alessandro Ghedini
On mar, giu 24, 2014 at 07:05:12 -0400, Samuel Bronson wrote: > Alessandro Ghedini writes: > > > On mar, giu 24, 2014 at 09:33:51 -0400, Samuel Bronson wrote: > > >> Well, I think I've figured it out; there are really *two* packages > >> wanting to be split off, an Arch:all package and an Arch:a

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2014-06-25 Thread Simon McVittie
On 25/06/14 00:05, Samuel Bronson wrote: > Yeah, I *did* notice that my changes won't just magically make things > better for dbus; it would, in fact, require patching configure.ac there > as well. However, what little mention I see of the pkg-config file on > valgrind's bug tracker is skeptical a

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2014-06-24 Thread Samuel Bronson
Alessandro Ghedini writes: > On mar, giu 24, 2014 at 09:33:51 -0400, Samuel Bronson wrote: >> Well, I think I've figured it out; there are really *two* packages >> wanting to be split off, an Arch:all package and an Arch:any package. > > This doesn't really solve anything though. AFAICT e.g. dbu

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2014-06-24 Thread Alessandro Ghedini
On mar, giu 24, 2014 at 09:33:51 -0400, Samuel Bronson wrote: > Control: tags -1 + patch > > Simon McVittie writes: > > > On 15/12/13 23:22, Alessandro Ghedini wrote: > >> While I still think this would be nice, it turned out to be a bit > >> more difficult to implement (basically the pkg-config

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2014-06-24 Thread Samuel Bronson
Control: tags -1 + patch Simon McVittie writes: > On 15/12/13 23:22, Alessandro Ghedini wrote: >> While I still think this would be nice, it turned out to be a bit >> more difficult to implement (basically the pkg-config file is >> generated at build time, and it can't be created if the configur

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2013-12-16 Thread Simon McVittie
On 15/12/13 23:22, Alessandro Ghedini wrote: > While I still think this would be nice, it turned out to be a bit > more difficult to implement (basically the pkg-config file is > generated at build time, and it can't be created if the configure > stage fails). Thanks for looking at this, anyway.

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2013-12-15 Thread Alessandro Ghedini
Control: reopen -1 Control: notfixed -1 valgrind/1:3.9.0-2 On Wed, Dec 04, 2013 at 06:22:21PM +0100, Alessandro Ghedini wrote: > Control: tags -1 pending > > On mar, dic 03, 2013 at 11:56:44 +, Simon McVittie wrote: > > Package: valgrind > > Version: 1:3.9.0-1 > > Severity: wishlist > > > >

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2013-12-04 Thread Alessandro Ghedini
Control: tags -1 pending On mar, dic 03, 2013 at 11:56:44 +, Simon McVittie wrote: > Package: valgrind > Version: 1:3.9.0-1 > Severity: wishlist > > It would be great if valgrind could ship memcheck.h and friends, and > valgrind.pc, in a new valgrind-dev or valgrind-headers or something on al

Bug#731228: valgrind: please provide valgrind client-request headers on all platforms

2013-12-03 Thread Simon McVittie
Package: valgrind Version: 1:3.9.0-1 Severity: wishlist It would be great if valgrind could ship memcheck.h and friends, and valgrind.pc, in a new valgrind-dev or valgrind-headers or something on all architectures; then packages that consume them, like dbus, wouldn't have to stay in sync with valg