Interpreting stacktraces

Andrew Conkling andrew.conkling at gmail.com
Wed Mar 19 12:00:06 GMT 2008


On Wed, Mar 19, 2008 at 12:29 AM, Brian Murray <brian at ubuntu.com> wrote:

> On Tue, Mar 04, 2008 at 10:09:38AM -0500, Andrew Conkling wrote:
> > I've become more involved in triage for a few packages and have often
> come
> > across stacktraces. Often I'm fairly sure I'm looking at duplicates of
> other
> > bugs, but it can be really hard to tell. Rather than continue to stare
> at
> > these bugs and traces blankly, I'm reaching out to see if there's any
> way I
> > can learn to interpret them.
>
> Emmet Hickory (persia) gave a class in November on interpreting stack
> traces to in #ubuntu-classroom.  I found the irc log at
> http://irclogs.ubuntu.com/2007/11/17/%23ubuntu-classroom.html but it may
> also be typed up better somewhere else.
>
> Is this the type of information you are looking for?
>

Hi Brian,
Thanks for the reply; I was just thinking about this yesterday as I came
across another bug with which I wasn't sure what to do. :)

Skimming that IRC log you linked to, that does indeed look like exactly the
info I need. Seems really interesting. I wish I could actually attend a lot
of these sessions, but they're always scheduled while I'm at work. :)

Offhand, do you know if any of the techniques change when I'm working with
non-C (Python, Mono) applications?

Thanks very much!
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20080319/6b273654/attachment.htm 


More information about the Ubuntu-bugsquad mailing list