[mythtv-users] mythfrontend crash

[Paul Harrison]

On 22/11/2021 18:30, James Abernathy wrote:

>
>
> On Mon, Nov 22, 2021 at 1:15 PM David Hampton via mythtv-users 
> <mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>> wrote:
>
>
>     Hi Jim,
>
>     Can you generate a stack trace from the core file?
>
>     David
>
>
> Unfortunately not with this crash. I'll have to wait until it happens 
> again. I'm in the process of building an automated script to do all 
> the backend stuff like setting up mariadb, mythweb, mythtv user, 
> mythtv/config.xml, XMLTV, etc.
>
> Since I could not reproduce the error, I blew away the system and 
> reinstalled it so I could test my script.  With the newest build I 
> have not had any issues.  So I'll have to wait until it happens again.
>
> Can you point me to how to generate a strack track from the core file??
>
> Jim A
>
>

If you have a core file you should be able to use

$ gdb path/to/mythfrontend path/to/corefile

and then do the usual

(gdb) thread apply all bt full

to print out the backtrace.


Usually on Ubuntu apport creates a .crash file that is a little more 
involved since first you have extract the .crash file to get the CoreDump :-

apport-unpack /var/crash/_usr_bin_mythfrontend.1000.crash ~/crashreport/

then in ~/crashreport/ you have a bunch of files including a CoreDump 
file. You can then use gdb to load the coredump and print the backtrace :-

gdb /usr/bin/mythfrontend ~/crashreport/CoreDump

(gdb) thread apply all bt full


You typically only get useful backtraces if the debug symbol for the 
program you are trying to debug is available and installed and sometimes 
you may need the debug symbols for some of the libraries used as well .


Paul H.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20211122/34184914/attachment.htm>