[mythtv-users] Segmentation fault when running mythfrontend
azmat.hussain at gmail.com
Wed Sep 26 14:55:20 UTC 2007
I ran mythfrontend through valgrind to see where the seg fault is
happening and received the following response:
2007-09-26 06:43:42.630 Registering Internal as a media playback plugin.
2007-09-26 06:43:45.010 MonitorRegisterExtensions(0x100, gif,jpg,png)
==17746== Stack overflow in thread 1: can't grow stack to 0xBE220FFC
==17746== Process terminating with default action of signal 11 (SIGSEGV)
==17746== Access not within mapped region at address 0xBE220FFC
==17746== at 0x52EBE71: ComboBoxSetting::addSelection(QString
const&, QString, bool) (in /usr/local/lib/libmyth-0.20.so.0.20.0)
==17746== ERROR SUMMARY: 17 errors from 6 contexts (suppressed: 138 from 1)
==17746== malloc/free: in use at exit: 3,980,944 bytes in 30,213 blocks.
==17746== malloc/free: 333,927 allocs, 303,714 frees, 38,081,790 bytes
Is this a clue for anyone?
On 9/25/07, Brandon Penglase <da5id2001 at spaceservices.net> wrote:
> On Tue, 25 Sep 2007 09:20:54 -0700
> Azmat <azmat.hussain at gmail.com> wrote:
> > Some more info. The frontend crashes right when I start it up. I see
> > the messages that Myth is loading and scaling the theme images, but
> > then it quickly dies. Here are the errors:
> > $ mythfrontend
> > 2007-09-24 08:03:10.827 Using runtime prefix = /usr/local
> > 2007-09-24 08:03:11.877 Database Hostname: filmfreak.arkham.net
> > 2007-09-24 08:03:12.131 DPMS is disabled.
> > 2007-09-24 08:03:12.503 New DB connection, total: 1
> > 2007-09-24 08:03:12.549 Connected to database 'mythconverg' at host:
> > filmfreak.arkham.net
> > 2007-09-24 08:03:12.551 Total desktop dim: 800x600, with 1 screen[s].
> > 2007-09-24 08:03:12.586 Using screen 0, 800x600 at 0,0
> > 2007-09-24 08:03:12.648 Current Schema Version: 1199
> > 2007-09-24 08:03:12.650 mythfrontend version: 0.21.20070910-2
> > www.mythtv.org 2007-09-24 08:03:12.650 Enabled verbose msgs:
> > important general 2007-09-24 08:03:14.422 Total desktop dim: 800x600,
> > with 1 screen[s]. 2007-09-24 08:03:14.424 Using screen 0, 800x600 at
> > 0,0 2007-09-24 08:03:14.460 Switching to wide mode (blootube-wide)
> > 2007-09-24 08:03:14.615 Using the OpenGL painter
> > mythtv: could not connect to socket
> > mythtv: Connection refused
> > 2007-09-24 08:03:14.645 lirc_init failed for mythtv, see preceding
> > messages 2007-09-24 08:03:14.645 Joystick disabled.
> > 2007-09-24 08:03:16.240 Loading from:
> > /usr/local/share/mythtv/themes/blootube-wide/base.xml
> > 2007-09-24 08:03:16.286 Loading from:
> > /usr/local/share/mythtv/themes/default/base.xml
> > 2007-09-24 08:03:16.583 Registering Internal as a media playback
> > plugin. 2007-09-24 08:03:17.308 MonitorRegisterExtensions(0x100,
> > gif,jpg,png) Segmentation fault
> Not sure if it helps, but I was getting seg faults when updating to
> 0.20.2 svn 14498, when I finally got a chance to run it through gdb, it
> appeared to be a libpng issue. I recompiled libpng, and all was well.
> (Note: I use Gentoo).
> > One thing to note is that I did get my frontend working when I first
> > upgraded to 0.20.2. With that build I ended up setting my frontend
> > gui's resolution to 800x600. I only started seeing the seg fault
> > after rebooting the machine. Could this be the problem? Is there
> > some way to reset the frontend gui to the default settings without
> > going through the gui?
> > Thanks again.
> > On 9/24/07, Justin The Cynical <cynical at penguinness.org> wrote:
> > > Azmat wrote:
> > > > My apologies. I'm running on an FC5 system (kernel ver
> > > > 2.6.17-1.2187_FC5).
> > > >
> > > > When I compiled my mythtv source I used the following
> > > > configuration: configure --enable-xvmc-opengl --enable-proc-opt
> > > > --enable-firewire --enable-lirc --enable-opengl-video
> > > > --xvmc-lib=XvMCNVIDIA --enable-opengl-vsync --enable-xvmc-vld
> > >
> > > I'd try removing --enable-opengl-video.
> > >
> > > Last time I tried that, performance was terrible. Granted, that was
> > > some time ago, but IIRC, that particular video rendering method is
> > > not really ready for usage yet.
> > >
> > > I could be wrong, and I'm sure if I am, others who are using it
> > > successfully will correct me. :-)
> > > _______________________________________________
> > > mythtv-users mailing list
> > > mythtv-users at mythtv.org
> > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > !DSPAM:46f9357e256861310711570!
More information about the mythtv-users