In my case, error 4 means “The cause was a user-mode read resulting in no page being found.”
As commenter “LittleAncientForestKami” explains, maybe not rocket science, but since I had no idea how to figure this out, really appreciated.
So, I thought I’d figure out what “rip” and “rsp” meant. “rsp” is probably a little hard to use, but “rip” is the address of the instruction where the crash occured, and you can figure out what function it points to using this technique described by StackOverflow user qrtt1:
Dump the addresses of the crashing application by saying “objdump -d ProcessNameThatCrashed | less” (where “ProcessNameThatCrashed” is the name of the crashing app)
Search for the address in ‘less’ by typing “/”, then entering the address name (in this case, the address I’m searching for is ‘81473d0’).
A few (or maybe many) lines up from the line matching the address in question, you should see the name of the function that crashed:
“brew install boost” (without the quotes). Notice errors. Try updating brew by doing a ‘brew update’. Failures. Notice by looking at /Users/<userid>/Library/Logs/Homebrew/boost/01.bootstrap.sh that “brew” is at version 0.95 on my machine. Research brew and see it’s on version 1.4.0. Reinstall Brew as though it’s never been installed (even though it is). Notice install says success despite printing a couple of errors during the install. Use “sudo rm /usr/local/share/man/man1/brew.1” and “sudo rm /usr/local/share/doc/homebrew” and re-install brew: /usr/bin/ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)” to fix.
Retry “brew install boost”. Success! And brew has installed the latest Boost (1.66.0); under the old version of brew it was trying to install version Boost 1.59.0.
So I installed IPython today. It was a bit of an adventure, so thought I’d document it here, in case it helps anyone else (including my future self, heh):
Installed Python 3.6 (the default, 2.7, included with macOS, isn’t new enough). This puts the “python3” executable on your machine, which you can invoke similarly to “python” (which will invoke the default OS-supplied Python, probably 2.7).
Got ‘pip‘. Note this was a convoluted process that involved copying some text from the pip website, pasting it into a text file, then executing that text file from python3 like so: ‘python3 get-pip.py’ (without the quotes). This yielded the ‘pip3.6’ executable, located here: /usr/local/bin/pip3.6
Used the ‘pip3.6’ executable to download ‘ipython’: /usr/local/bin/pip3.6 install ipython
Noticed that IPython looked like it installed correctly, but ‘ipython’ didn’t run from the command line immediately after that, and the installation path wasn’t noted anywhere in the installation output. Turns out, IPython added its installation location to my PATH via my .bash_profile file, but didn’t tell me. I reloaded my .bash_profile like this, and all was good: source ~/.bash_profile
Now I’ve got IPython! Invoke like this from the command line like this: ‘ipython’. Output looks like this:
Macintodffeb798:local me$ ipython
Python 3.6.3 (v3.6.3:2c5fed86e0, Oct 3 2017, 00:32:08)
Type ‘copyright’, ‘credits’ or ‘license’ for more information
IPython 6.2.1 — An enhanced Interactive Python. Type ‘?’ for help.In :
Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. This works by allocating a socket to listen to port on the local side, optionally bound to the specified bind_address. Whenever a connection is made to this port, the connection is forwarded over the secure channel, and a connection is made to host port hostport from the remote machine. Port forwardings can also be specified in the configuration file. IPv6 addresses can be specified with an alternative syntax:
[bind_address/]port/host/hostport or by enclosing the address in square brackets. Only the superuser can forward privileged ports. By default, the local port is bound in accordance with the GatewayPorts setting. However, an explicit bind_address may be used to bind the connection to a specific address. The bind_address of ”localhost” indicates that the listening port be bound for local use only, while an empty address or ‘*’ indicates that the port should be available from all interfaces.
-N will disable the ability to execute a remote command.
My 2009 27″ iMac is starting to show its age. So when its hard drive started crunching this morning (and bringing the machine to a crawl), I wanted to know a little more. The command-line utility fs_usage is good if there’s not much going on, but if there’s a lot, the information flies by far too quickly to get good sense of what’s going on.
fseventer — donation-ware by Robert Pointon of fernLighting — is a great way to figure out what’s going on. It provides the interesting information from fs_usage, but it does so in a fun, visual, animated way. Highly recommended.
Recently my Finder started crashing multiple times per day, so I opened up the Console application and looked for the crashlogs. Looks like Dropbox was the culprit. In each of the 14 Finder crashes I’ve had since November 4 2013, the following line appears in the crashing thread:
“This may have nothing to do with your Finder crashes, but do you have a Lion-compatible version of Dropbox installed?”
…which got me thinking. I’m running OS X 10.8.5. Looking at my Dropbox version (Menubar > Dropbox icon > Preferences > Account), I saw that my Dropbox version was 1.6.4 and that the software had no mechanism to autoupdate nor a way to “check for updates”.
So I checked Dropbox’s website, and lo-and-behold, the current version is 2.4.7, which I promptly installed. Hopefully this cures my woes!
So, I’ve moved in with my significant other (yay!), and part of that move is a reconfiguration of my office space. Part of this involves me examining things I’ve been holding onto for a while. Those things? Software packaging. Giant, shelf-space hogging, software packaging. Boxes, just filled with cardboard & plastic, so as to take up more space on retail shelves, so that they get noticed by consumers and picked up. I just recycled so much of that stuff.
Now that we’re in the age of electronic software distribution, that won’t be so much of a problem. That said, I couldn’t bear to part with my box for American McGee’s “Alice”, one of the first games I bought for the first computer I bought, all the way back in 2001. So there’s a part of me that regrets this loss of the physical manifestation of software, too. The future of software will be a colder place in that regard.