Bug 192488 - lang/ruby20 segmentation fault/coredump
Summary: lang/ruby20 segmentation fault/coredump
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Michael Moll
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-07 19:43 UTC by Patrick Gibson
Modified: 2015-11-16 20:35 UTC (History)
1 user (show)

See Also:

Attachments
stacktrace (45.00 KB, text/plain)
2014-08-07 19:43 UTC, Patrick Gibson 		no flags Details
Boot log (8.14 KB, text/plain)
2014-08-07 19:43 UTC, Patrick Gibson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Gibson 2014-08-07 19:43:25 UTC 
Created attachment 145479 [details]
stacktrace

We're doing some automatic publishing using Jekyll 1.5.1 using the ruby20 port via cron. Not every time, but several times a day, we're seeing a seemingly random segfault. Stacktrace is attached.
Comment 1 Patrick Gibson 2014-08-07 19:43:50 UTC 
Created attachment 145480 [details]
Boot log
Comment 2 John Marino freebsd_committer freebsd_triage 2014-08-07 19:55:41 UTC 
over to maintainer group...
Comment 3 Michael Moll freebsd_committer freebsd_triage 2014-11-13 12:49:21 UTC 
I'd suggest first to update all packages involved. Ruby and Jekyll (and especially dependencies like celluloid(using timers/hitimes)) got updated, bringing a lot of fixes.
Comment 4 Michael Moll freebsd_committer freebsd_triage 2015-11-16 20:20:59 UTC 
What's the status here?
Comment 5 Patrick Gibson 2015-11-16 20:34:13 UTC 
This may as well be closed. We've since moved onto Ruby 2.1 and 2.2 and are also using newer version of Jekyll and related plugins.
Comment 6 Michael Moll freebsd_committer freebsd_triage 2015-11-16 20:35:00 UTC 
thanks! closing...