getsegbyname(3) Mac OS X Developer Tools Manual Page

Mac Dev Center Mac OS X Reference Library General Mac OS X Man Pages

This manual page is part of Xcode Tools version 3.2.2

To obtain these tools:

Install the Xcode Tools from developer.apple.com.

If you are running a version of Xcode Tools other than 3.2.2, view the documentation locally:

In Xcode
In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

For more information about the manual page format, see the manual page for manpages(5).
For more information about this technology, look for other documentation in the Apple Reference Library.
For general information about writing shell scripts, read Shell Scripting Primer.


GETSEGBYNAME(3)                                                                              GETSEGBYNAME(3)



NAME
       getsegbyname - get the segment command for the named segment

SYNOPSIS
       #include <mach-o/getsect.h>

       const struct segment_command *getsegbyname(const char *segname);

DESCRIPTION
       This  routine  returns the segment_command structure for the named segment if it exists in the Mach-O
       (Mach object) executable getsegbyname(3) is linked into.  Otherwise getsegbyname(3) returns NULL.  It
       uses  the  link  editor  defined  symbol _mh_execute_header and just looks through the load commands.
       Since these are mapped into the __TEXT segment they are read-only and thus const by default.  If this
       is   to   be   used  in  executables  linked  with  -pie  then  the  value  return  by  the  call  to
       _dyld_get_image_vmaddr_slide(0) will need to be added to the  vmaddr  field  of  the  segment_command
       struct.

SEE ALSO
       end(3), getsectbyname(3)



Apple, Inc.                                    October 3, 2008                               GETSEGBYNAME(3)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors: Report errors in the content of this documentation with the feedback links below.
Bug reports: Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems: Report formatting mistakes in the online version of these pages with the feedback links below.

Did this document help you?