3 <title>Debugging with GDB
</title>
4 <meta http-equiv=
"Content-Type" content=
"text/html">
5 <meta name=
"description" content=
"Debugging with GDB">
6 <meta name=
"generator" content=
"makeinfo 4.3">
7 <link href=
"http://www.gnu.org/software/texinfo/" rel=
"generator-home">
12 Node:
<a name=
"SVR4%20Process%20Information">SVR4 Process Information
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"DJGPP-Native.html#DJGPP%20Native">DJGPP Native
</a>,
14 Previous:
<a rel=
"previous" accesskey=
"p" href=
"HP-UX.html#HP-UX">HP-UX
</a>,
15 Up:
<a rel=
"up" accesskey=
"u" href=
"Native.html#Native">Native
</a>
19 <h4 class=
"subsection">SVR4 process information
</h4>
21 <p>Many versions of SVR4 provide a facility called
<code>/proc
</code> that can be
22 used to examine the image of a running process using file-system
23 subroutines. If GDB is configured for an operating system with
24 this facility, the command
<code>info proc
</code> is available to report on
25 several kinds of information about the process running your program.
26 <code>info proc
</code> works only on SVR4 systems that include the
27 <code>procfs
</code> code. This includes OSF/
1 (Digital Unix), Solaris, Irix,
28 and Unixware, but not HP-UX or Linux, for example.
31 <dt><code>info proc
</code>
32 <dd>Summarize available information about the process.
34 <br><dt><code>info proc mappings
</code>
35 <dd>Report on the address ranges accessible in the program, with information
36 on whether your program may read, write, or execute each range.