[mythtv] frontend crash gdb

Steven Adeff adeffs.mythtv at gmail.com
Fri Mar 10 17:03:18 UTC 2006


On 3/9/06, Steven Adeff <adeffs.mythtv at gmail.com> wrote:
> On 3/9/06, Martin Ebourne <lists at ebourne.me.uk> wrote:
> > On Thu, 09 Mar 2006 10:34:22 -0500, Steven Adeff wrote:
> > > On 3/9/06, Isaac Richards <ijr at case.edu> wrote:
> > >> You're close. =)  You're cutting off the top bits - where it says where
> > >> it crashed.  Just include from the 'program exited with sigsegv at'
> > >> information on.
> > >>
> > >> Both of the crashes you sent seem to be dying in the LCD server
> > >> communication code..   Looks to me like it's probably due to unsafe
> > >> threaded usage of QSocket in the LCD class.  Would probably be better to
> > >> rewrite that to use QSocketDevice instead.
> > >>
> > >> Isaac
> > >
> > > Isaac, I'm glad to be able to produce somewhat usable gdb backtraces now.
> > > I don't know what I'm doing thats cutting off the top bits, so here is
> > > what I am doing, and hopefully you can tell me what I need to change in my
> > > process....
> >
> > The lines beginning 'program exited' that Isaac refers to are output by
> > gdb when you start it with a core file. You'll need to cut & paste those
> > onto the top of the backtrace you get with logfile enabled.
> >
> > Cheers,
> >
> > Martin.
>
> ok! I've gzip'd two new back traces. Let me know how these go.
>
> let me know if I should keep creating these or what.

when reading through the backtrace, what should I look for to see what
caused the crash? I'd like to be able to better identify things so I
know what to write up for tickets.

thanks,
--
Steve


More information about the mythtv-dev mailing list