Re: [Adhearsion] Segmentation fault after connection to asterisk.

[Luca Pradovera]

That looks like a Celluloid vs. your distro's shared libraries issue.
Did you have a look at Celluloid's issues?

--
Luca Pradovera
luca.pr...@gmail.com



Il giorno 03/mag/2013, alle ore 14:19, Rory Low <r.low...@gmail.com> ha scritto:

> <dump.txt>

[Ben Langfeld]

/home/rory85/.rvm/gems/ruby-2.0.0-p0/bundler/gems/celluloid-io-646c1d701428/lib/celluloid/io/reactor.rb:43: [BUG] Segmentation fault

You'll see the segfault is happening in the celluloid-io reactor. Celluloid-io has no C code itself, so it's likely this is buried in nio4r. The question is, why are you using celluloid-io from git, rather than a released version?

Regards,
Ben Langfeld

On 3 May 2013 15:19, Rory Low <r.low...@gmail.com> wrote:

I have completely re installed RVM, ruby,  and a fresh install of adhearsion and dependencies.

I've attached the trace log.  It seems no matter what version of ruby I use, the same segmentation fault occurs.

Some system information:

I'm running Arch Linux 64bit and it is completely up to date as of today.

Linux lithium 3.8.11-1-ARCH #1 SMP PREEMPT Wed May 1 20:18:57 CEST 2013 x86_64 GNU/Linux

ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-linux]

*** LOCAL GEMS ***

actionmailer (3.2.13)

actionpack (3.2.13)

activemodel (3.2.13)

activerecord (3.2.13)

activeresource (3.2.13)

activesupport (3.2.13)

adhearsion (2.3.1)

adhearsion-asterisk (1.3.1)

adhearsion-loquacious (1.9.3)

arel (3.0.2)

bigdecimal (1.2.0)

blather (0.8.4)

builder (3.0.4)

bundler (1.3.5)

celluloid (0.13.0)

celluloid-io (0.13.1)

coderay (1.0.9)

connection_pool (1.0.0)

countdownlatch (1.0.0)

deep_merge (1.0.0)

diff-lcs (1.2.4)

erubis (2.7.0)

eventmachine (1.0.3)

ffi (1.8.1)

future-resource (1.0.0)

girl_friday (0.11.2)

has-guarded-handlers (1.5.0)

hike (1.2.2)

i18n (0.6.1)

io-console (0.4.2)

journey (1.0.4)

json (1.7.7)

little-plugger (1.1.3)

logging (1.8.1)

mail (2.5.3)

method_source (0.8.1)

mime-types (1.23)

minitest (4.3.2)

multi_json (1.7.2)

niceogiri (1.1.2)

nio4r (0.4.3)

nokogiri (1.5.9)

polyglot (0.3.3)

pry (0.9.12.1)

psych (2.0.0)

punchblock (1.8.2)

rack (1.4.5)

rack-cache (1.2)

rack-ssl (1.3.3)

rack-test (0.6.2)

rails (3.2.13)

railties (3.2.13)

rake (10.0.4, 0.9.6)

rdoc (4.0.0, 3.12.2)

rspec (2.13.0)

rspec-core (2.13.1)

rspec-expectations (2.13.0)

rspec-mocks (2.13.1)

rubinius-actor (0.0.2)

rubinius-core-api (0.0.1)

ruby_ami (1.3.4)

ruby_fs (1.1.0)

ruby_speech (1.1.0)

rubygems-bundler (1.1.1)

rvm (1.11.3.7)

slop (3.4.4)

sprockets (2.2.2)

state_machine (1.2.0)

test-unit (2.0.0.0)

thor (0.18.1)

tilt (1.4.0)

timers (1.1.0)

treetop (1.4.12)

tzinfo (0.3.37)

I'm willing to provide any other information needed, just ask!

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

[Rory Low]

I have tried everything I can think of.  This last attempt (the one I submitted) was celluloid and adhearsion via git.  This segmentation fault occurs every time, no matter where I get the gems from.

If it will help,I can submit the trace from a fresh install of 1.9.3 and adhearsion from rubygems.

Thanks,

Rory

[Ben Langfeld]

Rory,

New versions of Adhearsion and Punchblock were released yesterday. Please just try using released version, and make sure you do a bundle update. If that still doesn't work, please file an issue on github.

Regards,
Ben Langfeld