Skip to content
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

x86_64 binaries. #22

Open
0vercl0k opened this issue Sep 22, 2013 · 3 comments
Open

x86_64 binaries. #22

0vercl0k opened this issue Sep 22, 2013 · 3 comments

Comments

@0vercl0k
Copy link

Hi,

It seems you have uploaded a bunch of compiled binaries (debugee, debugee_with_debug_info for example) but the thing is it has been compiled for x86_64 ; and it doesn't seem to be compiled during the installation process.

In my case I'm testing schem on a x86 guest system so of course it won't work without recompiling those files manually. I believe you've somehow forgot to add the buildings of those files in your make/setup process :).

Also, I encountered a problem with redis-server: the version of redis-server available in my package manager (aptitude) is 2.4 (which isn't supported by schem) so I had to manually compile a supported version like the 2.6.7. Maybe instead of relying on the package manager you can directly download the archive file redis-2.6.7.tar.gz and launch a compilation ? It would have helped me anyway!

Last thing, I also ended up modifying emserver.rb in order to make the http server listening on all the network interfaces ; you may want to add a switch in the command line for that!

Cheers,
0vercl0k

@eqv
Copy link
Member

eqv commented Sep 22, 2013

Thanks for setting up Schem and letting us know about the problems you encountered. They are all valid points and we will fix them.

  • The next makefile will build those files during setup.
  • The problem with redis is only a matter of how the config file is named (redis has the version in the expected config file name) - should be easy to fix.
  • The interface to listen on should indeed be a config option. Will be fixed shortly.

@0vercl0k
Copy link
Author

Hey thanks for the quick answer! Cool then!

By the way, I'm still struggling to make it works, I mean I managed to have the webui but this one is like empty like no process is being debugged. I don't see any specific errors in the log, I can see the gdb launched in the process list ; may be you have some pointers for me to debug the problem ?
Here is the log from the javascript console in my browser:

http://192.168.70.131:31337/ sockets.js:15
trying cmd.js:6
http://192.168.70.131:31337/ sockets.js:15
created cmdline cmd.js:21
http://192.168.70.131:31337/ sockets.js:15
trying dialog.js:6
http://192.168.70.131:31337/ sockets.js:15
created dialog spawner dialog.js:20
openend controll socket sockets.js:57
valid plugin sockets.js:34
openend controll socket sockets.js:57
valid plugin sockets.js:34

Uncaught TypeError: Cannot read property 'IP' of null struct.js:57

openend controll socket sockets.js:57
valid plugin sockets.js:34
openend controll socket sockets.js:57
valid plugin sockets.js:34
openend controll socket sockets.js:57
valid plugin sockets.js:34
openend controll socket sockets.js:57
valid plugin sockets.js:34
Array[2]
 lane.js:198
openend controll socket sockets.js:57
valid plugin sockets.js:34
Array[2]
 lane.js:198
openend controll socket sockets.js:57
valid plugin sockets.js:34
Array[3]
 lane.js:198
openend controll socket sockets.js:57
valid plugin sockets.js:34
31

Uncaught TypeError: Cannot read property 'top' of undefined 

Again thank for the good work, the project looks like awesome :).

@eqv
Copy link
Member

eqv commented Oct 1, 2013

I removed redis entirely from the project so the redis problems should be gone :)

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