|
From: Benjamin P. <ben...@we...> - 2011-08-24 15:00:14
Attachments:
build_lion.diff
|
Hello, I would like to get Valgrind to work on my laptop :) What is the best way to contribute patches? Attach them on bugzilla or send them to the mailing list? cheers, Benjamin |
|
From: Tom H. <to...@co...> - 2011-08-24 15:19:49
|
On 24/08/11 16:00, Benjamin Poulain wrote:
> I would like to get Valgrind to work on my laptop :)
>
> What is the best way to contribute patches? Attach them on bugzilla or
> send them to the mailing list?
Well searching bugzilla or the mailing list archives to see if, just
possibly, the subject of Lion might have been discussed before would be
a good starting point ;-)
To quote what Julian said on the users list this morning:
"The latest formal release (3.6.1) does not support it. However I am
working to make the svn trunk support it. This is being tracked at
https://bugs.kde.org/show_bug.cgi?id=275168, and progress updates
will be posted there first."
So that bug would be a most excellent place.
In general patches are better placed on the bug tracker to avoid them
getting lost.
Tom
--
Tom Hughes (to...@co...)
http://compton.nu/
|
|
From: Julian S. <js...@ac...> - 2011-08-24 17:59:13
|
> "The latest formal release (3.6.1) does not support it. However I am > working to make the svn trunk support it. This is being tracked at > https://bugs.kde.org/show_bug.cgi?id=275168, and progress updates > will be posted there first." > > So that bug would be a most excellent place. For this particular bug, though, I have a configure patch already in my tree. I can commit it, although AFAICT the resulting Memcheck is still unusable because the malloc/free intercepts are screwed up somehow. I will push more stuff into the repo as soon as I can. At the moment I'm trying to get large threaded apps to work, and am stuck in a mysterious swamp of spinlock hangs, segfaults and general threading weirdness. (As usual :-) J |