On Thu, 2008-12-04 at 10:53 -0500, Chris Lumens wrote: > I'm working on automatic data collection for bug reports. Part of this > involves writing a little command line tool so we can tell users "Hey > switch to tty2 and run this command to get everything we need", instead > of having to walk them through it. > > I thought it'd be nice if we could generate an anacdump.txt on demand, > to help debug where anaconda's stuck but hasn't crashed. The attached > patch causes anaconda to write /tmp/anacdump.txt when SIGUSR2 is > received. It requires the stuff Peter just mailed. > > I'm thinking it is probably better to do this via dbus, but that > involves making anaconda a dbus-aware thing (whatever that involves) and > seems like a battle for another day. Why not go all the way and have a command to run that will trigger the in-anaconda bug filing window? That way one doesn't have to deal with getting the dump.txt off to some other host and filing the bug. I've often wanted to file a bug at a certain point in anaconda but since there was no traceback I had to jump through hoops. (added bonuses for attaching a screenshot of the gui (minus the file a bug window) when filing bugs) -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
