Re: mythtv 0.25 segmentation faults with mythpreviewgen and mythmetadatalookup

Around about 16/04/12 21:18, Jerome Hettich typed ...
> and everything now seems to be working...
> no idea why this would be  - so any suggestions as to what was going on
> would be very helpful so I can prevent this happening again.

   If there was a small hole in the PRM deps., you may have been missing a 
0.25 lib. that was falling back to an old 0.24 one you still had installed 
(although .so numbering should account for that).

   Often some old lib detritus is left behind by myth upgrades due to RPM 
library name changes (e.g., not libmythx but libmythx_0.24 abd 
libmythx_0.25”).  Since by what you typed you blew away *all* myth RPMs, and 
pulled the *lot* in afresh, that would have cleared it all up.


   The sort of things I do in this sort of situation usually start with 
'strace problemprogram' to see what happens just before the crash, and in 
this case probably 'ldd /path/to/problemprogram' to see what libs it thinks 
it wants (watching for rogue versions) and 'strace -eopen problemprogram' to 
see what lib files it's actually opening.

   In this case I'd probably have removed *[Mm]yth*0.24* [is yum case 
dependant?] as well, as if it was a rogue library you'd have then got a 
run-time error reporting a missing library.

-- 
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit


_______________________________________________
atrpms-users mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-users