K Shea wrote:
> Alan S, thank you for the reply. I looked at that bug and it looks like it might be the same thing I experienced, and I note that a new version of Tvheadend is available so I'll try installing it over the weekend and see if it helps.
>
> I didn't really understand anything at all in that first link you sent. I am just a user, not a developer, and I can barely get around in Linux. I just install the stable build from the repository. If there is some build available with extra debugging help available, I have no idea where you get it or how to install it, not that I'd really want to anyway because I'd be afraid of losing my settings. What I guess I don't understand is, if the stable build isn't giving enough debugging information to help diagnose a crash, why not just include that extra debugging code in all builds instead of asking users to install some special build? Seems kind of silly to expect regular users, many of whom have a lot of difficulty getting regular Tvheadend installed and working, to then turn around and install some special build with "debugging symbols", whatever those are. Unless it would cause some performance issue,I'd say just put the "debugging symbols" in all builds so when someone tries to send information on a crash or bug, everything needed is already there.
I think there is a reason for not having the symbols built in. Open a feature request for it. :)
> Also, it would be good if you could turn on extra debugging from within the web interface, and not have to run Tvheadend in some special way, or do some Linux mumbo-jumbo.
There is! It's called the debugging tab :)
>
>(Also that page was obviously written by a programmer, and probably makes some sense to other programmers, but definitely not to just regular users!)
I'll look into writing a less technical guide :)
>
> And anyway, none of that would have helped here, because these crashes seem to happen at random.
> So even if I could somehow figure out how to enable extra debugging, I could not reproduce the issue at will. But all that aside, thank you very much for pointing me to that bug report and fix. It gives me some hope that this problem has already been addressed!
Look into installing corekeeper. That'll capture all core dumps that you can use with gdb.
<doc>