In this session we will look at low-level (Linux) system debugging tools to
find out what is going on (or wrong!) with your PHP environment, although the
techniques are also valid for other programs besides PHP. We will cover
debugging crashes with gdb, checking out memory leaks with valgrind, and many
other tools to find out what is going wrong, and hopefully, figure out why.

This session teaches tools to help out with tracking down bugs, and provides
information on how to get better at debugging connection issues, crashes, files
not being written, etc. The session is also valuable for people who want to
help out with providing good bug reports for Open Source projects.

Comments

Comments are closed.

A LOT of information to process after this talk.
The speakeer did an awesome job of showing what you need to deal when trying to debug underlying systems of php.
Live demos are always fun when they crash.

Great talk and reminder to use the low level tools

Rated 5

Van Belle Jonathan (Grummfy) at 15:53 on 27 Jan 2017

thanks, but it will require time to digest it.

Rated 5

Steve Guns at 16:47 on 27 Jan 2017

Great talk, might go too far / be too technical for some people but I loved it. Picked up a couple new things to try out. Next time I file a bug report it'll be better!

Rated 5

Robert Basic at 17:11 on 27 Jan 2017

I will be coming back to this talk and it's slides, it had a lot of useful information on what to do when things go wrong.

Rated 5

Thijs at 08:25 on 29 Jan 2017

Great talk. Fairly technical talk, explained very well, thank you.

Good talk, and live demo's are always a bit of a gamble, but I aquired enough information already to peak my interest in this matter. Well done

Rated 5

Ɓukasz at 09:32 on 30 Jan 2017

Amazing talk! Years of experience in less than hour. It should be recorded - I could use it as a reference when debugging.
@Derick Rethans please at least mak a blog post with all the commands that you've showed to us.

Thanks for the clear examples, great talk. Next time I encounter a segfault, I will try to look into it myself!