Os X Bus Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the
What Is Bus Error 10
company Business Learn more about hiring developers or posting ads with us Stack Overflow bus error mac Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 mac bus error 10 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Nasm Hello World Bus Error OS X up vote 0 down vote favorite I have the following assembly code
Bus Error 10 C++
(copied from here): hello.asm: section .data msg: db 'hello, world!', 0 section .text global _start _start: mov rax, 4 mov rdi, 1 mov rsi, qword msg ; I added qword because the compiler complained mov rdx, 13 syscall mov rax, 1 xor rdi, rdi syscall As explained in the comment above I added qword because I recieved the following error message: $ yasm -f macho64 hello.asm hello.asm:10: error: macho: sorry, cannot apply 32 bit absolute relocations in 64 bit mode, consider "[_symbol wrt rip]" for mem access, "qword" and "dq _foo" for pointers. After making that change, both compiling and linking succeed, but I get a bus error while running: $ yasm -f macho64 hello.asm $ ld -o hello -e _start hello.o $ ./hello bus error ./hello Is the addition of qword incorrect, or is there something else I need to change? osx assembly nasm share|improve this question edited Jul 1 '14 at 12:15 asked Jul 1 '14 at 1:58 cabellicar123 2,46811743 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote accepted 64-bit system calls on OSX need to have a class specifier in bits 24..31 of the register that holds the system call number (rax in your case). You've implicitly used the class specifier 0, which is invalid. You probably want the UNIX/BSD class, which means that you should be adding 2<<24 (0x2000000). So these lines: mov rax, 4 mov rax, 1 should be changed to: mov rax, 0x2000004 mov rax, 0x2000001 Also, I don't see what purpose that sub rsp, 8 at the end is serving, so you can probably remove that line. share|improve this answer answered Jul 1 '14 at 6:28 Michael 34k82863 The "sub rsp, 8" instruction
a title. You can not post a blank message. Please type your message and try again. NuTachyon Level 1 (1 points) Q: Bus error: 10 What is the meaning of: "Bus error: 10" I installed update 10.10.4 and my MacBook Pro 15 inch (early 2011) which has been running Yosemite has nearly impossible to use.Virtually any mouse click resulted in a couple minutes of the spinning beach ball before responding to requests. Ran disk utilities and fixed permissions. Ran slightly faster. Still unusable beach ball on each mouse click. I booted to safe boot mode to attempt to run a backup. It gave me an error message "can't http://stackoverflow.com/questions/24501442/nasm-hello-world-bus-error-os-x write to drive"I verified this new 2Tb external drive had no issues. Tried again. Same error. Them I rebooted to normal boot. Backup hung at approx 50Gb. Tried to retry safe boot mode, computer hung at point of loading desktop image. Gave it 2 hours to get past this point. Booted back in normal, attempted time machine again and based on a you-tube video, I went to console, searched for https://discussions.apple.com/thread/7145240?start=0&tstart=0 wdworker to search for errors...in on the system.log I find: (shortened for readability)...com.apple.xpc.launchd[1] (com.apple.mdworker.32bit.02000000-0000-0000-0000-000000000000 [6813]): Service exited due to signal: Bus error 10note 1: [6813] is incrementing for each entry. note 2: I tried to give full account of steps. A few iterations left out. note 3: I can give more detail as necessary. Anyone in Apple Land have a clue? MacBook Pro (15-inch Early 2011), OS X Yosemite (10.10), batt charge erratic since Yosemite Posted on Jul 25, 2015 2:29 AM I have this question too Close Q: Bus error: 10 All replies Helpful answers by Linc Davis, Linc Davis Jul 25, 2015 10:46 AM in response to NuTachyon Level 10 (208,044 points) Applications Jul 25, 2015 10:46 AM in response to NuTachyon Almost certainly the startup drive is failing, or there is some other internal hardware fault.Back up all data on the drive immediately if you don't already have a current backup. There are ways to back up a computer that isn't fully functional--ask if you need guidance.Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, indepen
Sign in Pricing Blog Support Search GitHub This repository Watch 70 Star 1,858 Fork 339 gruntjs/grunt-contrib-watch Code Issues 110 Pull requests 12 Projects https://github.com/gruntjs/grunt-contrib-watch/issues/204 0 Pulse Graphs Bus error in OS X 10.9 #204 Closed oskarrough opened this Issue Sep 9, 2013 · 66 comments Projects None yet Labels onhold wontfix Milestone No milestone Assignees No one assigned 49 participants and others oskarrough commented Sep 9, 2013 Hi, I realize I'm running a developer preview of OS X but before bus error I roll back to 10.8 I wanted to see if there's a fix to the following error. When a change is detected, the watch task breaks my 'grunt server' with the following: Running "watch" task Waiting...Bus error: 10 OS X 10.9 DP7 Node 0.10.18 Grunt 0.4.1 Generator-webapp 0.4.2 (didn't change a line in the code so gruntfile etc. are all bus error 10 the defaults) grunt member shama commented Sep 9, 2013 Sounds like an error upstream that will need to be addressed by https://github.com/joyent/libuv (or may have already). We can't fix that error from this plugin so I recommend staying on OSX 10.8 until node catches up. shama closed this Sep 9, 2013 spacenick commented Sep 17, 2013 Got the same issue; OS X 10.8.5 Running "watch" task Bus error: 10 grunt member shama commented Sep 17, 2013 @spacenick Oh really? Which version of node.js? spacenick commented Sep 17, 2013 Oops yea sorry, node v0.10.18 grunt-cli v0.1.9 grunt v0.4.1 grunt member shama commented Sep 17, 2013 Thanks! Still nothing we can likely do to fix that from here. I haven't ran into this issue and I'm on the same setup. If you can, creating a test repo that recreates the error would be much helpful. It was helpful in tracking down this previous watch error: nodejs/node-v0.x-archive#5463 spacenick commented Sep 17, 2013 Thanks @shama varju commented Sep 24, 2013 @spacenick Thanks; I assumed this was a 10.9 issue. Downgrading