From: Harm v. d. H. <ha...@et...> - 2001-11-03 23:21:24
|
On Sun, Nov 04, 2001 at 12:10:41AM +0100, Roy Sigurd Karlsbakk wrote: > > So my guess is a stale NAV plugin. > > > > I think it would be good if the part of xine-engine that pulls in all > > plugins sets the SIGSEGV handler, so that xine can > > a) exit nicely. > > b) tell which plugin is the offending one. > > > > At the moment, you just miss it because it prints after calling the > > plugin's init, not before. > > hm > > what can I do to disable the plugin? Well, deleting it usually works :-) A good practice when trying new xine versions is to first remove all files in /usr/local/lib/xine/plugins (or whatever your prefix is) and then do a 'make install' from xine-lib. If that doesn't help, removing HOME/.xinerc sometimes works wonders. But I'd still really like a SIGSEGV handler as outlined below to make the process of figuring out what's going wrong easier. Harm |