Mercurial > mplayer.hg
changeset 5127:621a68b911a9
hints on RTFM
author | arpi |
---|---|
date | Sat, 16 Mar 2002 01:56:19 +0000 |
parents | 1c55c0dd1570 |
children | a2aecc3bff4e |
files | mplayer.c |
diffstat | 1 files changed, 15 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/mplayer.c Sat Mar 16 01:34:45 2002 +0000 +++ b/mplayer.c Sat Mar 16 01:56:19 2002 +0000 @@ -378,9 +378,23 @@ // can't stop :( kill(getpid(),SIGKILL); } - mp_msg(MSGT_CPLAYER,MSGL_FATAL,MSGTR_IntBySignal,x, + mp_msg(MSGT_CPLAYER,MSGL_FATAL,"\n" MSGTR_IntBySignal,x, current_module?current_module:mp_gettext("unknown") ); + switch(x){ + case SIGINT: + case SIGQUIT: + case SIGTERM: + case SIGKILL: + break; // killed from keyboard (^C) or killed [-9] + case SIGILL: + mp_msg(MSGT_CPLAYER,MSGL_FATAL,"- MPlayer crashed by 'Illegal Instruction'. It usually happens when you run it on different CPU than it was compiled for. Verify this!\n"); + case SIGFPE: + case SIGSEGV: + mp_msg(MSGT_CPLAYER,MSGL_FATAL,"- MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. For details, see DOCS/bugreports.html section 5.b.\n"); + default: + mp_msg(MSGT_CPLAYER,MSGL_FATAL,"- MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, read DOCS/bugreports.html and follow instructions there. We can't and won't help unless you provide these informations when reporting a possible bug.\n"); + } exit_player(NULL); }