Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9115135
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T04:21:31+00:00 2026-06-17T04:21:31+00:00

The write syscall has the following functional prototype: size_t write(int, const void *buf, size_t

  • 0

The write syscall has the following functional prototype:

size_t write(int, const void *buf, size_t nbytes);

How do I call the write syscall using inline assembler in GCC under MacOS X?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-17T04:21:33+00:00Added an answer on June 17, 2026 at 4:21 am

    A generic solution to this type of question: Write a short test program doing the write() call you are interested in, and then use gcc -S to produce assembly or use otool to disassemble the binary; find out how the write() call was assembled and transform that into the appropriate inline assembly.

    (edit) To see the actual syscall, follow the library call in the assembly code. In the example of write(), following the indirections will lead you via libSystem.B.dylib to _write in libsystem_kernel.dylib, which you can disassemble using otool.

    (edit2) Full example below, using this test program test.c:

    #include <stdio.h>
    int main(void)
    {
        char buf[] = "test\n";
        ssize_t n;
        n = write(2, buf, sizeof(buf));
        return n;
    }
    

    Compile and test, using -O1 -fverbose-asm to get concise, readable machine code:

    % gcc -O1 -fverbose-asm -o test test.c
    % ./test
    test
    

    Use otool to disassemble main() in the test binary:

    % otool -p _main -tvV test
    test:
    (__TEXT,__text) section
    _main:
    0000000100000ef0    pushq   %rbp
    0000000100000ef1    movq    %rsp,%rbp
    0000000100000ef4    subq    $0x10,%rsp
    0000000100000ef8    leaq    0xfa(%rbp),%rsi
    0000000100000efc    movb    $0x74,0xfa(%rbp)
    0000000100000f00    movb    $0x65,0xfb(%rbp)
    0000000100000f04    movb    $0x73,0xfc(%rbp)
    0000000100000f08    movb    $0x74,0xfd(%rbp)
    0000000100000f0c    movb    $0x0a,0xfe(%rbp)
    0000000100000f10    movb    $0x00,0xff(%rbp)
    0000000100000f14    movl    $0x00000002,%edi
    0000000100000f19    movl    $0x00000006,%edx
    0000000100000f1e    xorb    %al,%al
    0000000100000f20    callq   0x100000f32 ; symbol stub for: _write
    0000000100000f25    addq    $0x10,%rsp
    0000000100000f29    popq    %rbp
    0000000100000f2a    ret
    

    List the libraries test is dynamically linked against to find _write:

    % otool -L test
    test:
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)
    

    Try to locate _write in libSystem.B.dylib:

    % otool -p _write -tvV /usr/lib/libSystem.B.dylib
    /usr/lib/libSystem.B.dylib:
    (__TEXT,__text) section
    Can't find -p symbol: _write
    

    Check the dependencies of libSystem.B.dylib:

    % otool -L /usr/lib/libSystem.B.dylib
    /usr/lib/libSystem.B.dylib:
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)
        /usr/lib/system/libcache.dylib (compatibility version 1.0.0, current version 47.0.0)
        /usr/lib/system/libcommonCrypto.dylib (compatibility version 1.0.0, current version 55010.0.0)
        /usr/lib/system/libcompiler_rt.dylib (compatibility version 1.0.0, current version 6.0.0)
        /usr/lib/system/libcopyfile.dylib (compatibility version 1.0.0, current version 85.1.0)
        /usr/lib/system/libdispatch.dylib (compatibility version 1.0.0, current version 187.9.0)
        /usr/lib/system/libdnsinfo.dylib (compatibility version 1.0.0, current version 395.11.0)
        /usr/lib/system/libdyld.dylib (compatibility version 1.0.0, current version 195.6.0)
        /usr/lib/system/libkeymgr.dylib (compatibility version 1.0.0, current version 23.0.0)
        /usr/lib/system/liblaunch.dylib (compatibility version 1.0.0, current version 392.38.0)
        /usr/lib/system/libmacho.dylib (compatibility version 1.0.0, current version 800.0.0)
        /usr/lib/system/libmathCommon.A.dylib (compatibility version 1.0.0, current version 2026.0.0)
        /usr/lib/system/libquarantine.dylib (compatibility version 1.0.0, current version 36.6.0)
        /usr/lib/system/libremovefile.dylib (compatibility version 1.0.0, current version 21.1.0)
        /usr/lib/system/libsystem_blocks.dylib (compatibility version 1.0.0, current version 53.0.0)
        /usr/lib/system/libsystem_c.dylib (compatibility version 1.0.0, current version 763.13.0)
        /usr/lib/system/libsystem_dnssd.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/system/libsystem_info.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/system/libsystem_kernel.dylib (compatibility version 1.0.0, current version 1699.26.8)
        /usr/lib/system/libsystem_network.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/system/libsystem_notify.dylib (compatibility version 1.0.0, current version 80.1.0)
        /usr/lib/system/libsystem_sandbox.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/system/libunc.dylib (compatibility version 1.0.0, current version 24.0.0)
        /usr/lib/system/libunwind.dylib (compatibility version 1.0.0, current version 30.0.0)
        /usr/lib/system/libxpc.dylib (compatibility version 1.0.0, current version 77.19.0)
    

    Guess that _write is probably contained in libsystem_kernel.dylib (or alternatively try all of them):

    % otool -p _write -tvV /usr/lib/system/libsystem_kernel.dylib | head -20
    (__TEXT,__text) section
    _write:
    0000000000017fd4    movl    $0x02000004,%eax
    0000000000017fd9    movq    %rcx,%r10
    0000000000017fdc    syscall
    0000000000017fde    jae 0x00017fe5
    0000000000017fe0    jmp cerror
    0000000000017fe5    ret
    0000000000017fe6    nop
    0000000000017fe7    nop
    [...]
    

    Now we have all the assembly we need to construct the inline assembly version of test:

    #include <stdio.h>
    int main(void)
    {
        char buf[] = "test\n";
        ssize_t n;
        asm volatile (
            "movl $0x00000002, %%edi\n"  /* first argument */
            "movl $0x00000006, %%edx\n"  /* third argument */
            "movl $0x02000004, %%eax\n"  /* syscall number */
            "syscall\n"
            : "=A"(n)         /* %rax: return value */
            : "S"(buf));      /* %rsi: second argument */
        return n;
    }
    

    Compile and test:

    % gcc -O1 -fverbose-asm -o test-asm test-asm.c
    % ./test-asm
    test
    

    That seems to work. The inline assembly above is not very refined; for example, you could pass in the first and third arguments dynamically as well, instead of hardcoding them in the assembly code.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

is it possible to write a single character using a syscall from within an
I'm trying to call the system call write with the inline assembler (gcc 4.2.1,
Valgrind throws me out this error: ==11204== Syscall param write(buf) points to uninitialised byte(s)
Write a NASM macro: divide, which has 2 arguments, which specify unsigned integers in
Write a NASM macro: divide, which has 2 arguments, which specify unsigned integers in
I write a project using Prism . I have tow modules and this modules
What process state has when it calls a syscall? I mean, don't asume it's
i try to write a system call. I followed these steps: linux/arch/x86/kernel/syscall_table_32.S ----> .
Why do we write *bufp = buf since both are arrays so in my
I am trying to write a system call of my own. It would just

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.