cvs: php-bugs-web / bugs-generating-backtrace.php

sean Thu Mar 31 17:58:22 2005 EDT Modified files: /php-bugs-web bugs-generating-backtrace.php Log: grammar and spelling http://cvs.php.net/diff.php/php-bugs-web/bugs-generating-backtrace.php?r1=1.2&r2=1.3&ty=u Index: php-bugs-web/bugs-generating-backtrace.php diff -u php-bugs-web/bugs-generating-backtrace.php:1.2 php-bugs-web/bugs-generating-backtrace.php:1.3 --- php-bugs-web/bugs-generating-backtrace.php:1.2 Sun Dec 16 10:50:27 2001 +++ php-bugs-web/bugs-generating-backtrace.php Thu Mar 31 17:58:19 2005 @@ -77,23 +77,22 @@ the bug report, along with any other details you can give us about your setup, and offending script.</p> -<h3>Locating which function call caused segfault:</h3> +<h3>Locating which function call caused a segfault:</h3> -<p>You can locate function call that caused segfault easily with gdb. -First you need core file or generate segfault under gdb as desccribed +<p>You can locate the function call that caused a segfault, easily, with gdb. +First, you need a core file or to generate a segfault under gdb as described above.</p> -<p>In PHP, function is executed by internal function called +<p>In PHP, each function is executed by an internal function called <b><code>execute()</code></b> and has its own stack. Each line -generated by <b><code>bt</code></b> command represents function call -stack. Typically, you will see several -<b><code>execute()</code></b> when you issue -<b><code>bt</code></b>. You are interested in the last -<b><code>execute()</code></b> stack. (i.e. smallest frame -number) You can move stack currently working with +generated by the <b><code>bt</code></b> command represents a function call +stack. Typically, you will see several <b><code>execute()</code></b> lines +when you issue <b><code>bt</code></b>. You are interested in the last +<b><code>execute()</code></b> stack (i.e. smallest frame +number). You can move the current working stack with the <b><code>up</code></b>, <code>down</code> or -<b><code>frame</code></b>command. Below is an example gdb session and -you can do the same for your segfault. </p> +<b><code>frame</code></b> commands. Below is an example gdb session that can +be used as a guideline on how to handle your segfault.</p> <ul> <li>Sample gdb session</li> @@ -125,14 +124,15 @@ </ul> <p>In this session, frame 3 is the last <b><code>execute()</code></b> -call. <b><code>frame 3</code></b> command move current working stack -to the frame.<br /> +call. The <b><code>frame 3</code></b> command moves the current working stack +to the proper frame.<br /> <b><code>print (char *)(executor_globals.function_state_ptr->function)->common.function_name</code></b><br /> -prints function name. In sample gdb session, pg_result_error() call -is causing the segfault. You can print any internal data as you want +prints the function name. In the sample gdb session, the +<code>pg_result_error()</code> call +is causing the segfault. You can print any internal data that you like, if you know the internal data structure. Please do not ask how to use gdb or about the internal data structure. Refer to gdb manual for gdb usage -and PHP source for the internal data structure.</p> +and to the PHP source for the internal data structure.</p> <p>You may not see <b><code>execute</code></b> if the segfault happens without calling any functions.</p>