This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

joint Valgrind + gdb devroom at FOSDEM 2018: proposal


Dear Valgrind and gdb hackers,

Please have a look at FOSDEM 2018 devroom proposal.
Let me know your comments, suggestions, etc.
The deadline is tomorrow (20th September).

I.


-------------------------------------------------------
Title: Valgrind, gdb, debugging tools
Coordinator: Ivo Raisr
Coordinator email: ivosh@ivosh.net
Secondary contact: Mark Wielaard (if Mark has no strict objections)
Secondary email: mark@klomp.org

Description:
The valgrind and gdb hackers would like to meet during FOSDEM 2018.

Several core developers said they would like to attend a hacker meeting
to meet each other in person and to coordinate various topics. And we
would like to invite other hackers of toolchain projects to discuss
cross project ideas.

Subjects for core hackers, new developers, users, packagers and cross
project functionality, that we would like to discuss and give
presentations on include:

- The recently added functional changes (for valgrind and gdb users).
- Get feedback on what what kinds of new functionality would
  be useful. Which tools and functionality users would like to see.
(valgrind and gdb users).
- How to add simple Valgrind features (adding syscalls for a platform or VEX
  instructions for a architecture port). (new Valgrind core developers).
- Infrastructure changes to the JIT framework. (core hackers).
- Discuss release/bugfixing strategy/policy (core hackers, packagers).
- Packaging Valgrind and gdb for distros, handling patches, suppressions, etc.
  (packagers).

Coordinator's affinity to the topic of the devroom:
core hacker, Solaris port maintainer

Why does it fit FOSDEM
Valgrind is an instrumentation framework for building dynamic analysis
tools. There are Valgrind tools that can automatically detect many
memory management and threading bugs, and profile your programs in
detail. You can also use Valgrind to build new tools.

GDB, the GNU Project debugger, allows you to see what is going on
`inside' another program while it executes -- or what another program
was doing at the moment it crashed.

Valgrind and GDB is Open Source / Free Software, and is freely
available under the GNU General Public License, version 2.

Relevant URLs:
Valgrind website: http://www.valgrind.org
GDB website: https://www.gnu.org/software/gdb/

Timeslot:
Half day

Special requirements:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]