Would "Core :: Debugging: gdb" be a good bugzilla component?

Right now the gecko gdb pretty-printers have been tracked using bugs in "Core :: Build Config" because that's where the bug that first added them lived. That component currently has 1773 bugs in it, 3 of which involve gdb, and with daily activity of ~10 bugs a day. I think a more targeted

Re: Would "Core :: Debugging: gdb" be a good bugzilla component?

You could also just file things like that in the corresponding component, and maybe create some kind of meta bug for gdb hooks. So debugging for nsTArray would be filed in XPCOM, etc. I think that's the way it works for Javascript engine related debugging hooks. Failing that, having the nested gdb

Re: Would "Core :: Debugging: gdb" be a good bugzilla component?

I think a meta bug would meet all the requirements. - You'd have to tell people about the component anyway, just as you would a metabug. - Components have textual names instead of numbers, but you can give bugs names that you can use in the blocker field. - You can get mail for new bugs added