Re: bugsquad guidelines



<snip>
> > Crashers
> > -- Immediately Critical+High
> > -- simple-dup-finder.cgi
> > -- Put crashing function in square brackets in the description if it is a new one
> 
> Perhaps we should explain how to find this function in the stack-trace.
> 
> > ---- This normally involves skipping through g_* and gtk_* and grabbing first application-specific frame
> ??
</snip>

That was my vague attempt at explaining how to find a crashing function
(it's more indented than the others....)

-- 
Andrew

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GS/M d--(-) s: a17 C++(+++) UL+ P++ L+++ E--- W+>++ N(-) o? K? w--(---)
!O M V-
PS+ PE Y+ PGP+>++++ t@ 5-- X- R tv-@ b++++ DI+++ D>---- G- e- h! r--- y?
------END GEEK CODE BLOCK------




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]