Bus Error Os X
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 company
Bus Error 10 Mac Os X
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs bus pirate os x Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers,
Bus Error C++
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 (copied from here): bus error linux 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 bus error core dumped 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,46311743 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 33.6k82863 The "sub rsp, 8" instruction may also cause problems: In Windows many system instructi
Support Search GitHub This repository Watch 2,404 Star 37,000 Fork 8,327 nodejs/node-v0.x-archive Code Issues 5,000+ Pull requests 41 Projects 0 Wiki Pulse Graphs New issue Bus Error on https://github.com/nodejs/node-v0.x-archive/issues/6251 Mac OS 10.9 DP8 #6251 Closed wedgeV opened this Issue Sep 20, 2013 · 20 comments Projects None yet Labels fs macintosh Milestone No milestone Assignees No one assigned 10 participants wedgeV commented https://groups.google.com/d/topic/nodejs/5LvewZ8oF0Y Sep 20, 2013 getting a bus error crash when running coffee with -w, I suppose this is an issue with node. node 0.10.18 with mac os 10.9 dp8. this is the output bus error when run from a debugger: * thread #2: tid = 0x143349, 0x00007fff964bd583 CarbonCore`FSEventsClientProcessMessageCallback + 39, stop reason = EXC_BAD_ACCESS (code=2, address=0x1007f5f48) frame #0: 0x00007fff964bd583 CarbonCore`FSEventsClientProcessMessageCallback + 39 CarbonCore`FSEventsClientProcessMessageCallback + 39: -> 0x7fff964bd583: callq 0x7fff964add4d ; FSEventsD2F_server 0x7fff964bd588: movq (%rbx), %rax 0x7fff964bd58b: cmpq -16(%rbp), %rax 0x7fff964bd58f: jne 0x7fff964bd59b ; FSEventsClientProcessMessageCallback + 63 Node.js Foundation member bnoordhuis commented Sep 20, 2013 /cc @indutny - not sure if we bus error os want to accept bug reports for Developer Preview versions of OS X but I'll let you decide. tjfontaine commented Sep 20, 2013 we probably should try and get ahead of this, I have a dev account and a laptop at home I can use for such things, I'll get it upgraded this weekend in preparation neekey commented Oct 5, 2013 Same problem, reference to this issue: gruntjs/grunt-contrib-watch#204 Node.js Foundation member indutny commented Oct 5, 2013 @tjfontaine any news? Can you post FSEvents.h as a gist and send me a link? bnoordhuis added a commit to joyent/libuv that referenced this issue Oct 5, 2013 bnoordhuis … This commit reverts the following commits: 983fa68 darwin: fix 10.6 build error in fsevents.c 684e212 fsevents: use shared FSEventStream ea4cb77 fseven
from GoogleSign inHidden fieldsSearch for groups or messages