Reading stack traces from bug reports

[Emilio Pozuelo Monfort]

Hello all!

Emmet Hikory has volunteered for running a session about how to read stack
traces (thanks Emmet!).


(quoting from wikipedia):
"A stack trace (also called stack backtrace or stack traceback) is a report of
the active stack frames instantiated by the execution of a program. They are
mostly used to aid debugging by showing where exactly an error occurs. The last
few stack frames often indicate the origin of the bug."

So knowing them well means you will be able to triage a lot of more bug reports,
and possibly fixing them. Also, since these reports are usually crashes they are
very important, so don't doubt this is an incredible opportunity for learning a
very important stuff.

It will be run this Saturday at 11:00 UTC on #ubuntu-classroom on Freenode. So
if you are interested on it, just join us there! It will be a really interesting
session and we will learn a very useful thing, with our master persia.

So don't forget to come, and also let your friends know about this, so they can
join too!

See you there,
Emilio


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20071114/3a417418/attachment.pgp 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20071114/3a417418/attachment-0001.pgp