The Eleventh Annual Southern California Linux Expo
February 22-24, 2013
Hilton Los Angeles International Airport

Submitting a proper Postgres bug report


In those rare situations when you find a new bug in an opensouce project, the likelihood of getting timely relevant help is often directly related to the quality of your question. Using a real life example of a bug I reported to Postgres, this talk will cover the steps you should follow, including:

* Boiling the problem down to a simple case
* Confirming it is in fact a new bug
* Obtaining the source and creating a debug build
* Generating a core dump
* Using GDB (with the core) to find and diagnose the crash
* Examining the source to determine the cause
* Where and how to report it
* Following up on your report to help with the fix

A good chunk of this should apply to any project, not just Postgres.

Century AB
Friday, February 22, 2013 - 16:30 to 17:30