Segmentation fault: 11 with latest macports .25

[John Damore]

I just upgraded to the latest macports mythtv version  .25 and now i'm getting a Segmentation fault: 11 in mythtv error every time I start torc. 

any one else have this problem?

[Robert McNamara]

I know there was a period early in .25 where the Myth devs introduced a number of crashes into the Services API.  If the MacPorts version falls in there, it's possible the app tickles the bug.  Anecdotally, the .25.3 release is the most stable for users of the app with .25, though anything after .25.3 should be fine too, as well as any .26 version.

Solutionwise, I'd see if you can get the revision bumped to something newer (or less likely, to something older).  I am not aware of any crash issues in the Services API with latest .25-- just the old versions.

Robert

On Tue, Aug 13, 2013 at 4:56 PM, John Damore <jjda...@gmail.com> wrote:

I just upgraded to the latest macports mythtv version  .25 and now i'm getting a Segmentation fault: 11 in mythtv error every time I start torc. 

any one else have this problem?

--
You received this message because you are subscribed to the Google Groups "Torc for iOS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to torc-for-ios...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Robert McNamara]

If the version they're still building is the one referenced here:

https://trac.macports.org/ticket/35934

Then it's from July of 2012 and is missing about a year's worth of fixes.  That said, I suppose there could be something funky going on with the MacPorts build itself... but my first instinct would be to try to get to absolute newest .25 (or roll back to your previous working build, or try .26).

Robert

[John Damore]

Sorry I should have noted the version I'm at!

I'm at  fixes/0.25 [v0.25.3-ed3b7d10-MacPorts] www.mythtv.org

So I think the version looks good. I might try back leveling, there is a .26 version on macports, but I'm not sure if i can backlevel from there easily

[Robert McNamara]

OK-- yeah, .25.3 should be the best performing of the .25 releases... if it segfaults, then it makes me suspect the build process somewhere.  Obviously MythTV shouldn't segfault when asked to respond to calls to its own APIs.  If it's happening at app startup, then the relevant API calls would be GetRecordedList, GetVideoList, GetUpcomingList, and GetEncoderList.  This may give you somewhere to start.  If rolling back doesn't help, then you'll probably need to get a version with debug symbols built so that we can submit a ticket to the MythTV people (or maybe to the Macports builder?)

Robert

[pvr4me]

Late reply but...

If you have problems with MacPorts, please report it via the macports-users mailing list.  I'd be interested to know exactly where this segfault is triggered.  I don't use Torc but Myth via MacPorts has been very stable.  Do you have an OS X crash report?

Regarding .25 v. .26, the issue really is with Myth.  The first time you run 0.26, your database is upgraded to the new schema.  To go back to 0.25, you have to drop the database and restore a 0.25 backup which means that any new or expired recordings become a problem.  Other than that, MacPorts makes it dead simple to deactivate the old version before installing the new one.  Cookbook instructions are at:

http://www.mythtv.org/wiki/Building_Myth_for_Mac_with_MacPorts

Craig

(maintainer of the MythTV ports on MacPorts.)