|
From: Mark W. <mj...@re...> - 2014-01-13 15:05:31
|
Hi Valgrind hackers, developers and users, Valgrind will have a devroom at FOSDEM 2014 on Sunday 2 February with the follow talks: Valgrind Support in the Eclipse IDE Roland Grunberg 10:00 10:25 Testing of valgrind RPMs in RHEL Miroslav Franc 10:30 10:55 SimuVEX Yan Shoshitaishvili 11:00 11:50 Helgrind: a constraint-based data race detector Julian Seward 13:00 13:50 Porting Valgrind on Solaris Ivo Raisr, Petr Pavlu 14:00 14:25 GDB, so where are we now? Pedro Alves 15:00 15:25 Combining the power of Valgrind and GDB Philippe Waroquiers 15:30 15:55 BoF: Valgrind and GDB integration Tom Tromey 16:00 16:25 BoF: Ideas, new features and directions for Valgrind Mark Wielaard 16:30 17:45 More background information about the talks can be found at: https://fosdem.org/2014/schedule/track/valgrind/ For the last session we are still looking for ideas to discuss. It will be an open discussion, so anything you like can be discussed. The current list of discussion topics is: * Release/bugfixing strategy/policy. * Valgrind and transactional memory. * Making Valgrind really multi-threaded, parallelising Memcheck, parallelising the rest of the framework, and tools. * Better support compiled/JITted code. Allowing the JIT compiler to indicate to Valgrind the link between the JITted code and the source code. * Modify memcheck to report the last leaked pointer to a block integrate "omega" as a memcheck option or omega as a separate tool. http://www.brainmurders.eclipse.co.uk/omega.html * Should we continue to support MacOS? What about Valgrind on MS-Windows? * Make Callgrind work sanely on ARM. * Redo the JIT framework to reduce baseline overheads. * Packaging valgrind for distros, handling patches, suppressions, etc. * Flexible heuristic possibly leaked support. i.e. let the user specific an "expression" in a suppression file that if true would transform a possibly leaked into a reachable. * An interactive SQL relational interface to Valgrind data structures https://github.com/mfragkoulis/PiCO_QL/tree/master/src/Valgrind-mod I'll update the abstract of the BoF with the above and any other topics people will bring up: https://fosdem.org/2014/schedule/event/valgrind_bof/ If you want to put something on the Valgrind BoF agenda please send a small description (one or two paragraphs) to the the moderator Mark Wielaard mj...@re... with in the subject: "FOSDEM devroom discuss: ..." If you want to discuss a somewhat larger topic please do feel free to send two or three slides in advance. Mark will collect ideas/suggestions/... and present these and coordinate the discussion (and keep track of the time, so every idea will be discussed). Call For Video Volunteers The FOSDEM organization can provide us with equipment to record some or all of the talks in our devroom. But we need at volunteers to do the actual recordings. An ideal candidate for this job would be someone who is going to be watching talks in the Valgrind devroom most (or all) of the time anyway, and who doesn't mind watching after a camera and/or an audio mixer while watching the talk. While some A/V experience is obviously useful for the volunteer, it is absolutely not required; FOSDEM will provide the right gear and help set it up, and FOSDEM organizers will also provide enough information so the volunteers know what to do. This will include a live training session during the opening talk (in Janson) for those who want it. If you can and want to help record talks/discussions in the Valgrind devroom that would be really appreciated. |
|
From: Mark W. <mj...@re...> - 2014-01-13 17:25:57
|
On Mon, 2014-01-13 at 16:04 +0100, Mark Wielaard wrote: > Hi Valgrind hackers, developers and users, > > Valgrind will have a devroom at FOSDEM 2014 on Sunday 2 February with > the follow talks: Apologies for messing up the formatting. Here it is again, hopefully better readable. If not, please just see: https://fosdem.org/2014/schedule/track/valgrind/ 10:00 - 10:25 Valgrind Support in the Eclipse IDE An Overview of the Eclipse Valgrind plugin provided by the Linux Tools Project Roland Grunberg 10:30 - 10:55 Testing of valgrind RPMs in RHEL Miroslav Franc 11:00 - 11:50 SimuVEX Using VEX in Symbolic Analysis Yan Shoshitaishvili 13:00 - 13:50 Helgrind: a constraint-based data race detector Julian Seward 14:00 - 14:25 Porting Valgrind on Solaris Ivo Raisr, Petr Pavlu 15:00 - 15:25 GDB, so where are we now? Status of GDB's ongoing target and run control projects Pedro Alves 15:30 - 15:55 Combining the power of Valgrind and GDB Philippe Waroquiers 16:00 - 16:25 BoF: Valgrind and GDB integration Crazy and fun ways to make the Valgrind/GDB combo more powerful Tom Tromey 16:30 - 17:45 BoF: Ideas, new features and directions for Valgrind Open discussion about small (or big) ideas to improve or change Valgrind. Mark Wielaard > More background information about the talks can be found at: > https://fosdem.org/2014/schedule/track/valgrind/ > > For the last session we are still looking for ideas to discuss. It will > be an open discussion, so anything you like can be discussed. The > current list of discussion topics is: > > * Release/bugfixing strategy/policy. > * Valgrind and transactional memory. > * Making Valgrind really multi-threaded, parallelising Memcheck, > parallelising the rest of the framework, and tools. > * Better support compiled/JITted code. Allowing the JIT compiler to > indicate to Valgrind the link between the JITted code and the source > code. > * Modify memcheck to report the last leaked pointer to a block integrate > "omega" as a memcheck option or omega as a separate tool. > http://www.brainmurders.eclipse.co.uk/omega.html > * Should we continue to support MacOS? > What about Valgrind on MS-Windows? > * Make Callgrind work sanely on ARM. > * Redo the JIT framework to reduce baseline overheads. > * Packaging valgrind for distros, handling patches, suppressions, etc. > * Flexible heuristic possibly leaked support. i.e. let the user specific > an "expression" in a suppression file that if true would transform a > possibly leaked into a reachable. > * An interactive SQL relational interface to Valgrind data structures > https://github.com/mfragkoulis/PiCO_QL/tree/master/src/Valgrind-mod > > I'll update the abstract of the BoF with the above and any other topics > people will bring up: > https://fosdem.org/2014/schedule/event/valgrind_bof/ > > If you want to put something on the Valgrind BoF agenda please send a > small description (one or two paragraphs) to the the moderator Mark > Wielaard mj...@re... with in the subject: "FOSDEM devroom > discuss: ..." If you want to discuss a somewhat larger topic please do > feel free to send two or three slides in advance. Mark will collect > ideas/suggestions/... and present these and coordinate the discussion > (and keep track of the time, so every idea will be discussed). > > Call For Video Volunteers > > The FOSDEM organization can provide us with equipment to record some or > all of the talks in our devroom. But we need at volunteers to do the > actual recordings. An ideal candidate for this job would be someone who > is going to be watching talks in the Valgrind devroom most (or all) of > the time anyway, and who doesn't mind watching after a camera and/or an > audio mixer while watching the talk. > > While some A/V experience is obviously useful for the volunteer, it is > absolutely not required; FOSDEM will provide the right gear and help set > it up, and FOSDEM organizers will also provide enough information so the > volunteers know what to do. This will include a live training session > during the opening talk (in Janson) for those who want it. > > If you can and want to help record talks/discussions in the Valgrind > devroom that would be really appreciated. |
|
From: Mark W. <mj...@re...> - 2014-02-10 12:10:19
|
Hi all, Thanks for all you who came to Valgrind devroom at FOSDEM. I think the interest in the talks surprised us all. We had to turn away some people at some talks because the room was just full. For those who missed it most slides are attached to the talk pages listed at: https://fosdem.org/2014/schedule/track/valgrind/ (only the SimuVEX one is still missing). We also did try to record videos of the talks, but that wasn't a great success. We were missing a firewire cable at the start, so couldn't record anything. Then when we did get that cable the audio was really bad/silent. Sorry about that. The FOSDEM video staff is trying to rescue what is possible. If they are able to, the videos will turn up at: http://video.fosdem.org/2014/ (we were in K4201 on Sunday - which currently doesn't have any videos yet). Lesson learned for next time: - If we are doing video recordings we really need to find someone that is dedicated to doing that instead of having someone do it on the side. The FOSDEM staff offered a little training beforehand, but nobody had time to attend that training. - We had a relaxed schedule with some extra "free" time so people could get some lunch and drinks in between. But that did mean some talks had not enough time allocated for them (25 minutes really isn't that much). And we did run out of time during the last BoF session. We should allocate a bit more time per talk if possible (or at least warn that 25 minutes is too short for both a talk and a demo), and instead of a BoF with lots of small issues we should push for some lightning talks (mini BoFs) in between the larger talks. Maybe combined with a BoF at the end to use some more time for lightning subjects that could use some more discussion. - We really should organize some social get together before/after the technical talks. Just pick a pub for drinks or a restaurant for dinner to meet up. Thanks, Mark |