Re: triaging and marking dups - a warning and advice



On Mon, 2002-02-25 at 14:04, Wayne Schuller wrote:
[snip]

> 2. Look for patterns in the stack traces of the 69333 dup list and
> create some more specific tracker bug for each stack trace, and move the
> dups to the proper report.
> When you do this, remember to put the crashing function in sqaure
> brackets in the report description where all the dups are marked. (and
> probably post to this list telling us where you are marking the dups, so
> we don't do it in 2 different places)

I remember rumors about instructions on how to figure out what the
crashing function was, but I've never seen them.  How do I figure this
out?
	Greg

-- 
Portland, Oregon, USA.




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