EL5 *** buffer overflow detected ***: /usr/bin/ruby terminated about stomp

[gmallard]

I doubt we are going to be much help with that. The gem is pure Ruby, no C involved.

We are not the only gem that fails to install in exactly this way on RHEL/CentOS 5 systems, see below.

But please show me the output of:

ruby -v

gem -v

ruby -r rbconfig -e 'puts Config::CONFIG["configure_args"]'

For background, see:

brianmario/yajl-ruby#89

auxesis/visage#84

https://raw.github.com/gist/1186912/325a3eae7cad43a56c39ad05e8237edf821b44a4/capistrano_install_install_buffer_overflow

http://pastebin.com/mLDxkBcF

And there are numerous others.....

[sgzijl]

Will supply the requested information when I'm at work, next tuesday.

On Jan 13, 2012, at 8:33 PM, Guy M. Allard wrote:

I doubt we are going to be much help with that. The gem is pure Ruby, no C involved.

We are not the only gem that fails to install in exactly this way on RHEL/CentOS 5 systems, see below.

But please show me the output of:

ruby -v

gem -v

ruby -r rbconfig -e 'puts Config::CONFIG["configure_args"]'

For background, see:

brianmario/yajl-ruby#89

auxesis/visage#84

https://raw.github.com/gist/1186912/325a3eae7cad43a56c39ad05e8237edf821b44a4/capistrano_install_install_buffer_overflow

http://pastebin.com/mLDxkBcF

And there are numerous others.....

---

Reply to this email directly or view it on GitHub:
https://github.com/morellon/stomp/issues/26#issuecomment-3484922

[gmallard]

I will add several notes, and a proposed solution. This actually has absolutely nothing to do with stomp.

I can recreate this in a CentOS 5.6 VM.

The root cause is that in your Redhat environment, there are bug(s) in your current 'tar' / 'zip' functionality. I suggest you eventually address that with maintenance from the package management system.

Experiments

Using that CentOS with:

• Ruby 1.8.5 (2006-08-25)
• gem 1.3.5

I attempted to install that gem file, and received the same results as you, a lovely stack trace.

Stomp 1.2.0 was built with a very current version of the gem command, probably 1.8.x (I do not remember which Ruby version I was using when I built the gem).

You are running gem version in the range 1.3.1 - 1.3.5 I would guess.

I experimented: on my Debian box, I used Ruby 1.8.5 (2008-06-20 patchlevel 231) and gem command version 1.3.5 to rebuild the stomp 1.2.0 gem, and copied that gem to the CentOS VM.

In CentOS I then re-attempted install of the new gem file. This succeeds!!

Proposed Solution

Proposed solution: send me an email address or point me to a free file share system you have access to. I will provide you with a new 'stomp-1.2.0.gem' file that should hopefully install.

[gmallard]

I am going to close this because of the lack of a response.

If you need further assistance, please let us know. Reopen this or create a new issue if necessary.