Question about bug #75835, getting started on bug-squad

Kees Cook kees at ubuntu.com
Mon Dec 18 21:48:28 GMT 2006


Hi Hilario,

On Mon, Dec 18, 2006 at 07:46:36PM +0100, Hilario J. Montoliu wrote:
> Comparing some stacktraces from several of the attached crash reports on
> those bug reports (using apport-unpack) they look very similar (though
> I'm not a developer so I might be wrong).

What is weird about this and other Firefox crashes I've looked at is 
that a SEGV happens via a raise(), and the stack seems to end up getting 
a bit trashed (0x0000000b, 0x00000000, ...)

If there was a little more definitive information in the crashes, I 
would recommend a bugpattern[1] be created for it.  I did that for the 
common Flash crashes, seen in bug 14911, and the JS crash from bug 
69003.  (Looks like bug 45008 would be the master bug for this problem?)

> Should I mark those bug reports as duplicates and confirm them? What do
> you think? I mean, how are you sure a bug report is a duplicate? When
> are you sure you have to confirm a bug? 

Many of the reports are very low on details, so I would at least merge 
those together.  They're all reporting the same observed behavior so 
until there's proof that there are separate causes, I'd say it's safe to 
merge common reports.

> As I've said I'm the noob here, and the last thing I want to do is
> messing up! :P

No problem!  Anyone giving thought to bug triage is already doing great 
work.  :)  Thanks!


[1] https://lists.ubuntu.com/archives/ubuntu-devel/2006-October/021502.html

-- 
Kees Cook
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20061218/3da5bee9/attachment.pgp 


More information about the Ubuntu-bugsquad mailing list