Skip to content

Bizarre directory structure created; possibly result of jruby itself #1928

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
timmc opened this issue Aug 28, 2014 · 1 comment
Closed

Bizarre directory structure created; possibly result of jruby itself #1928

timmc opened this issue Aug 28, 2014 · 1 comment
Milestone

Comments

@timmc
Copy link

timmc commented Aug 28, 2014

This is a long shot -- I don't even know if jruby is at fault, but I felt it was worth tossing in here. (Previously filed against RVM as rvm/rvm#3007; I was told to check here instead.)

This is in my home directory, and I don't know what created it:

bc-timmc:~$ tree -a Java\ HotSpot\(TM\)\ 64-Bit\ Server\ VM\ warning\:\ You\ have\ loaded\ library\ /
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /
└── home
    └── timmc
        └── .rvm
            └── rubies
                └── jruby-1.7.3
                    └── lib
                        └── native
                            └── arm-Linux
                                └── libjffi-1.2.so which might have disabled stack guard. The VM will try to fix the stack guard now.\012It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.\012
                                    └── home
                                        └── timmc
                                            └── .rvm
                                                └── rubies
                                                    └── jruby-1.7.3
                                                        └── lib
                                                            └── ruby
                                                                └── gems
                                                                    └── shared

18 directories, 0 files

It sounds like maybe a script piped the results of a command straight to shell. It could be anything up or down the stack, and I don't relaly know how to figure out where, but I'm posting this in case it rings a bell. Feel free to close if you feel this really is impossible to pin down.

@kares
Copy link
Member

kares commented Jun 11, 2018

defunct by now, also 1.7 is no longer supported. 9K is expected to be fine.

@kares kares closed this as completed Jun 11, 2018
@kares kares added this to the Non-Release milestone Jun 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants