Hacker News Reader

Comment by 0x0 | Hacker News Reader

Meanwhile, if you try to run the system lldb on the system ruby interpreter on OSX, you get this:

  % lldb ruby
  (lldb) target create "ruby"
  Current executable set to 'ruby' (x86_64).
  (lldb) run
  error: process exited with status -1 
  (cannot attach to process due to System Integrity Protection)

View on HN

Reboot in safe mode (⌘+R immediately after booting), open a terminal, run:

  csrutil disable

Reboot.

  -> % lldb ruby 
  (lldb) target create "ruby"
  Current executable set to 'ruby' (x86_64).
  (lldb) run
  Process 436 launched: '/usr/bin/ruby' (x86_64)

I for one am glad that it's now much harder to scam my grandparents.

That disables a lot of useful protections, seems overkill just to be able to trace a ruby script :-/

In that case, you should probably just not use the system ruby.

You can also disable just the relevant bits - `csrutil enable --without debug` would probably do the trick here.

And this is why I won't ever switch to OS X full time, and I'll stay with Linux for all my systems level programming. The low level tools just aren't there. With Linux, I've got gdb, objdump, strace, what have you. I'd have to compile most systems level tools from source on Apple laptop.

It's great for app developers, but I mainly do systems level things for personal projects, and I don't want to have to compile _tools_ from scratch. The hardware is awesome and I love the shiny box and the sleek design. I've been using a macbook pro all summer, and the only thing that I'm sold on is the hardware design / case. The charger is nice too.

What's with the tone here? You sound pretty angry while making an argument that largely boils down to "different tools are better for different use cases".

cp /usr/bin/ruby ~/Desktop/ruby

lldb ~/Desktop/ruby

:-)

cp `which ruby` ~ ; lldb ~/ruby

Reply on news.ycombinator.com