similar to: std::runtime_error when calling EM::stop

Hi everyone, If you subclass EventMachine::Connection and call it outside an EventMachine::run event loop, EventMachine crashes! Example: class Put < EventMachine::Connection include EventMachine::Deferrable HOST="localhost" PORT=8080 def self.request(data) EventMachine.connect(HOST, PORT, self) {|c| c.instance_eval { @data = data } } end #

I upgraded from 12.2 to 12.4 and found that my happy little eventmachine processes die with: terminate called after throwing an instance of ''std::runtime_error'' what(): call SetTlsParms before calling StartTls Here''s what I believe is the relevant snippet of my code, which calls start_tls() in the connection_completed() callback: connection =

Hi EM Gurus, I''m hoping someone can shed some light on the following... I''m using a 3rd party (legacy) server that can accept up to 8 simultaneous connections on one port. I''ve been able to make multiple connections to this server from within one call to EventMachine::run {...}. Specificaly, I can access each connection separately using: em_thread = Thread.new do

Hi all Is the EventMachine website (www.rubyeventmachine.com) down? I can''t access it from South Africa, and have tried using tor as well with no luck. I''m kinda new to EventMachine, so I first have a lot of examples to work through and reading to do before I start pestering the mailing list with questions. Thanks to everyone who partook in creating the library, so far

I know this error has been reported before, but a couple ppl have reported getting this randomly when running Thin and it crashed the server: terminate called after throwing an instance of ''std::runtime_error'' what(): unable to delete epoll event: Bad file descriptor I think it''s fixed on trunk now so I''m telling people that have this issue to checkout

Hello, on the application that I''m working on, we are using Thin. The server implements long polling and commands that alter its internal state. Connecting to the long poll is a very fast operation, while updating the state of the server is a relatively slow operation. The long poll connection is held open until there is a change to be sent to the connection. Here is my current

Hi, list Now I am coding for one non-blocking httpclient based on event-machine, and it seems the client will hang for 50 seconds if the destination is unreachable. My questions are 1. How can I short the timeout? I had tried conn.set_comm_inactivity_timeout(5), but it didn''t work 2. How can I add TimeoutHandler to the connection? Thanks! /Jack -- Jack Tang Software

I''m using the current release branch from the repository (version_0) on freebsd 6.1 with ruby 1.8.4. This is the error that is generated when running the code below at the bottom of the message, plus a gdb bt. Sorry no debugging symbols built into ruby but maybe the bt will help anyways. terminate called after throwing an instance of ''std::runtime_error'' what():

What repository should I pull from to get the latest snapshot of the EM java code for jruby? cr

# Everything is done on Mac OS X 10.8.4, with llvm/clang/libc++/libc++abi built from source this morning # totclang is an alias for the built clang. $ export LLVM=/Sources/LLVM $ export LIBCXX=$LLVM/libcxx $ export LIBCXXABI=$LLVM/libcxxabi $ totclang -std=c++11 -stdlib=libc++ -I $LIBCXX/include -fsanitize=undefined ubsan.cpp -L $LIBCXX/lib -L $LIBCXXABI/lib -lc++abi $

Hi all, I am encountering the following crash-causing bug using popen on occasion. I haven''t been able to narrow it down yet, but I am curious if anyone else has seen it or may have more information for me: Workers::DviToPng::PipeProtocol > terminate called after throwing an instance of ''std::runtime_error'' > what(): unable to reap subprocess > Abort trap

In "Understanding the Linux Kernel" 3rd edition, section 4.7 "Softirqs and Tasklets" it states: "Activation and execution [of defferable functions] are bound together: a deferrable function that has been activated by a given CPU must be executed on the same CPU. There is no self-evident reason suggesting that this rule is beneficial for system performance. Binding the

Ok, here is the class, I want to Unit Test, its part of a large app and is based on EventMachine library. I want to mock the class TickServer ( i.e not stub it) . Since in actual scenario, you can''t do this on this class: @server = TickServer.new # will toss an exception at your face you must initialize the server like this: EventMachine.run {

Hi David, Sorry to hear. Has anyone followed up with you yet? I've continued to dig in to this in my spare time and I've found the issue. It's a use-after-free, rather than any sort of memory smashing. ORC is currently failing to deregister the EH-frame section when the JIT is torn down (but *is* deallocating the memory for it). Normally that's not disastrous (though it does

Hi David, Thanks very much for that. I'll continue to dig in as time permits, and I'll update the bug report with my progress once it's filed. Cheers, Lang. On Mon, Apr 17, 2017 at 6:42 PM, David Lurton <dlurton at gmail.com> wrote: > Thanks Lang. I think I'll go the bug creation route. I have an email out > to llvm-admin requesting an account on bugs.llvm.org.

Hi All, I''m currently looking into doing a bit of evented network programming in ruby and i''m currently looking into packet, eventmachine and rev. The problem is that I need to be able to fork and start a new reactor within the forked child (it also should open a socket and write status information back to the main process). I have not been able to do this with EventMachine.

Friends, I am writing an event system which has an interface on a web site which can create events. The creation of events opens up EventMachine::run and connects to the event server, and sends messages. The problem comes if this is run inside of say, event driven mongrel, where it will crash fatally, the same as: EventMachine::run { EventMachine::run { } } The only solution that

Hello, I get a crash in my program that uses exceptions and the LLVM JIT, even though the exceptions are controlled and thrown/catched in a part that doesn't deal with LLVM. I noticed that llvm-config --cxxflags includes the -fno-exceptions flag. Do I need to throw no exceptions whatsoever in my application to use LLVM JIT? As a minimal example, I modified the code in

Firstly, apologies if this is not the right place to be asking this question--feel free to point me in the correct direction. I could be doing something wrong here but stackoverflow didn't feel like the correct place for this since there's so little there about LLVM ORC. Basically, I have a reproduction case (below) where if I throw an exception before I call JITSymbol::getAddress()

The following program is a minor variant on the sample given in the README with eventmachine-0.8.1. I am running under CentOS 4.5 (kernel 2.6.9-55.0.2.plus.c4) with a ruby-1.8.5 RPM from the CentOS testing repository. When I run it, I find that set_comm_inactivity_timeout doesn''t do anything. That is, if I client opens a connection, it stays open indefinitely. However, if I comment out