We have program from the valgrind devroom that will take place duringFosdem in Brussels on Saturday 5 February 2017:https://fosdem.org/2017/schedule/track/valgrind/

The last session will be the Valgrind BoF and Hackaton!

We need your help for that session! The simplest way to help is to justshow up and discuss anything you like and then start hacking! But it isalso fun to have a little structure to the session by letting us knowbeforehand what you think we should discuss and/or hack on.

Here is the current desciption, please help improve it:

Valgrind BoF and HackatonOpen discussion of ideas for Valgrind - and then we hack!https://fosdem.org/2017/schedule/event/valgrind_hackaton/

Come and hack on Valgrind together. Open discussion about small (or big)ideas to improve or change Valgrind.

Valgrind developers and users are encouraged to participate either bysubmitting ideas/suggestions or by joining the discussion. And of courseby kindly (or bitterly) complain about bugs you find important that arestill Not YET solved for that many years!?@!!!

Afterwards we will sit together and try to fix or implement some of thethings discussed.

Discuss any kind of possible improvement (technical or functional) toValgrind.

If you want to put something on the agenda please send a smalldescription (one or two paragraphs) to the the moderator Mark Wielaard***@redhat.com with in the subject: "FOSDEM devroom discuss: ..." If youwant to discuss a somewhat larger topic please do feel free to send twoor three slides in advance.

Mark will collect ideas/suggestions/... and present these and coordinatethe discussion (and keep track of the time, so every idea will bediscussed).

Some discussion topic ideas:

* Release/bugfixing strategy/policy.* Can we move to git yet?* Valgrind and transactional memory.* Making Valgrind really multi-threaded, parallelising Memcheck,parallelising the rest of the framework, and tools.* Instant leak detector. Modify memcheck to report the last leakedpointer to a block. Integrate "omega" as a memcheck option oromega as a separate tool.http://www.brainmurders.eclipse.co.uk/omega.html* Make Callgrind work sanely on ARM (and PPC). The Callgrindalgorithm to track call and return is to be improved to workproperly on these platforms. Is there a way to make this better?E.g. by having a fast way working in most cases, and rely onunwind info in the difficult cases. Can we detect atinstrumentation time that an instruction is a difficult case?* Packaging valgrind for distros, handling patches, suppressions,etc.* 32-bit x86 vs modern instruction sets (avx, etc.)* VEX is in theory cross-architecture. What would it take to makevalgrind cross-arch? How about starting with i686 on x86_64?* Which CPUID is it anyway? Valgrind isn't completely consistentin handling host CPU capabilities vs VEX emulation capabilities.What can we do to improve that? Make it user tunable?* <YOUR SUGGESTION HERE!>

This is a reminder that our valgrind devroom meeting at Fosdem,Brussels, is this Saturday. For detials, see below.

Also please let me know if you have any issues you want to discussduring the valgrind hackaton event (even if you cannot come, youcan submit ideas!)

If you are giving a presentation earlier on the day, but have somebonus slides that you might not have time to present (we will be stricton time) then feel free to sent them to me and/or feel free to suggestyou present the extra bonus material at the hackaton.

Post by Mark WielaardHi Valgrind users, hackers and enthusiasts,We have program from the valgrind devroom that will take place duringhttps://fosdem.org/2017/schedule/track/valgrind/The last session will be the Valgrind BoF and Hackaton!We need your help for that session! The simplest way to help is to justshow up and discuss anything you like and then start hacking! But it isalso fun to have a little structure to the session by letting us knowbeforehand what you think we should discuss and/or hack on.Valgrind BoF and HackatonOpen discussion of ideas for Valgrind - and then we hack!https://fosdem.org/2017/schedule/event/valgrind_hackaton/Come and hack on Valgrind together. Open discussion about small (or big)ideas to improve or change Valgrind.Valgrind developers and users are encouraged to participate either bysubmitting ideas/suggestions or by joining the discussion. And of courseby kindly (or bitterly) complain about bugs you find important that areAfterwards we will sit together and try to fix or implement some of thethings discussed.Discuss any kind of possible improvement (technical or functional) toValgrind.If you want to put something on the agenda please send a smalldescription (one or two paragraphs) to the the moderator Mark Wielaardwant to discuss a somewhat larger topic please do feel free to send twoor three slides in advance.Mark will collect ideas/suggestions/... and present these and coordinatethe discussion (and keep track of the time, so every idea will bediscussed).* Release/bugfixing strategy/policy.* Can we move to git yet?* Valgrind and transactional memory.* Making Valgrind really multi-threaded, parallelising Memcheck,parallelising the rest of the framework, and tools.* Instant leak detector. Modify memcheck to report the last leakedpointer to a block. Integrate "omega" as a memcheck option oromega as a separate tool.http://www.brainmurders.eclipse.co.uk/omega.html* Make Callgrind work sanely on ARM (and PPC). The Callgrindalgorithm to track call and return is to be improved to workproperly on these platforms. Is there a way to make this better?E.g. by having a fast way working in most cases, and rely onunwind info in the difficult cases. Can we detect atinstrumentation time that an instruction is a difficult case?* Packaging valgrind for distros, handling patches, suppressions,etc.* 32-bit x86 vs modern instruction sets (avx, etc.)* VEX is in theory cross-architecture. What would it take to makevalgrind cross-arch? How about starting with i686 on x86_64?* Which CPUID is it anyway? Valgrind isn't completely consistentin handling host CPU capabilities vs VEX emulation capabilities.What can we do to improve that? Make it user tunable?* <YOUR SUGGESTION HERE!>And now is the time on Sprockets when we hack!