On 11/05/13 09:27, John Baldwin wrote:
> One of my previous employers maintained a database of panics and I added ways
> to recognize "known panics" and tag them.  I ended up relying a lot on stack
> trace details from specific OS versions to mark a panic as an instance of a
> specific bug.  Also, you may have very different stack traces even on the same
> build version for a single bug.  In the case of my employer we had a
> constrained set of kernel configs and specific build versions to work with.
> It might be harder to correctly match panics in the wild what with patched
> trees and random kernel configs.

Right, I'm sure there will be panics I can't match up against anything else --
but this is fine.  If I get enough panic reports, I can still get useful data
out even if some of them aren't immediately usable.

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to