Lourens Veen <[EMAIL PROTECTED]> writes: > Yesterday, MPlayer crashed on me. In itself that's not so > interesting, but what was interesting was their crash handler. A > message popped up explaining that MPlayer had crashed, and that > that was a bug. Then it proceeded to explain how to get basic > debugging info, with a reference to a web page explaining how to > submit bug reports. It also told me not to expect any reply unless > I followed these rules to the letter. > > I'm wondering, would this be a useful feature for CDRecord? It could > print such a message when an error occurs, perhaps with a command > line switch to turn it off for expert users who know that what > they're doing might go wrong, or for use in shell scripts that only > want a return value. > > I know there's a feature freeze now, but perhaps this could be > included before the next release still? I bet a lot of people will > upgrade and have problems, this may well be a good way to manage > the chaos a bit better.
Well, this kind of crash handler is just a signal handler - some code which is executed when the operating system tells a process (a program being executed) that it has done something way wrong. It replaces the default behaviour of dumping the core. So the process has to do something what the operating system can recognize as being wrong. By now I never saw cdrecord crashing in this way. cdrecord certainly outputs SCSI error messages if something goes wrong, but these are errors detected by cdrecord itself. The operating system stays completely cool about them. So what's needed is some translation of plain SCSI error messages to instructions what could be done to fix it. However this is a feature already wished for a dozen times, which requires knowledge about: - SCSI MMC standards & Co - the hardware out there and its behaviour - the behaviour of involved software like the operating system (for all the many flavours and versions) There was already the idea of extracting the mailings to this list to a database for easiness of search. Well, I personally go with a searchable mailing list archive. Regards, Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
