[sldev] Community QA process

Jason Giglio gigstaggart at gmail.com
Fri Apr 24 09:17:10 PDT 2009


GDB Backtrace on an *unstripped* binary, along with a little about what
you were doing when it happened, is probably enough info to fix 80% of
the bugs.

What I do to make an unstripped binary is to change the strip command in
the makefiles to a cp command.  This way I know it's exactly the same
build, just unstripped.

Which bug did you get chewed out on?

-Jason

lists.secondlife.com at trap.wereanimal.net wrote:
> How does on enter a crash report on the pjira? I've tried a while back to 
> report one of thousand of random crashes everyone is complaining about and got 
> chew out for reporting it.
> 
> Is there a guide for posting gdb bt to the pjira? What gdb commands output 
> would the programmers like to see?
> 
> --Techwolf Lupindo


More information about the SLDev mailing list