Backport #5299
closed
Segmentation fault when using TweetStream gem in ruby 1.9.3
Added by dushyanth (Dushyanth Maguluru) over 13 years ago.
Updated over 13 years ago.
Description
=begin
=== Using tweetstream gem like this results in segfault:
TweetStream::Client.new('username','password').track('term1', 'term2') do |status|
puts "#{status.text}"
end
=== Environment:
ruby 1.9.3dev (2011-09-02 revision 33163) [x86_64-linux]
CentOS 5.2 (2.6.18-238.19.1.el5.centos.plus)
=== Attached files:
(1) List of gems installed (bundler's Gemfile)
(2) Ruby trace
(3) GDB trace
=end
Files
Please note that this happens outside of a rails app as well.
- Status changed from Open to Closed
- % Done changed from 0 to 100
This issue was solved with changeset r33231.
Dushyanth, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
- Tracker changed from Bug to Backport
- Project changed from Ruby master to Backport193
- Status changed from Closed to Assigned
- Assignee set to kosaki (Motohiro KOSAKI)
- Priority changed from Normal to 6
- Target version deleted (
1.9.3)
Yes, it's regression. we need to backport it soon.
Does "backport it soon" means backport it for the 1.9.3 release? I hope the answer is yes, its a pretty important bug for us.
Does "backport it soon" means backport it for the 1.9.3 release? Â I hope the answer is yes, its a pretty important bug for us.
Yes, I mean backport it for 1.9.3p0.
- Status changed from Assigned to Closed
This issue was solved with changeset r33258.
Dushyanth, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0Like0Like0