Re:Debugging using system calls in Mac OS X
by 0x0 on Saturday July 30, 2016 @04:59PM
(#12194673)
Meanwhile, if you try to run the system lldb on the system ruby interpreter on OSX, you get this:
[ Parent
| 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 :-/
Re:Debugging using system calls in Mac OS X
by ptomato on Saturday July 30, 2016 @08:30PM
(#12195230)
You can also disable just the relevant bits - `csrutil enable --without debug` would probably do the trick here.
Re:Debugging using system calls in Mac OS X
by Redoubts on Saturday July 30, 2016 @07:25PM
(#12195071)
In that case, you should probably just not use the system ruby.
Re:Debugging using system calls in Mac OS X
by ryanlm on Saturday July 30, 2016 @10:37PM
(#12195485)
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.
Re:Debugging using system calls in Mac OS X
by umanwizard on Saturday July 30, 2016 @11:07PM
(#12195566)
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".
[dead]
Then maybe you're not qualified to make such judgements?
Re:Debugging using system calls in Mac OS X
by umanwizard on Sunday July 31, 2016 @02:05PM
(#12198030)
But you already said you understand the utility for some people. That's the glory. Yours is a use case that's probably that of fewer than 0.1% of people who own Macs.
Re:Debugging using system calls in Mac OS X
by zZorgz on Saturday July 30, 2016 @08:18PM
(#12195198)
cp /usr/bin/ruby ~/Desktop/ruby
lldb ~/Desktop/ruby
:-)
Re:Debugging using system calls in Mac OS X
by umanwizard on Saturday July 30, 2016 @11:09PM
(#12195572)
cp `which ruby` ~ ; lldb ~/ruby