Home/ Questions/Q 7565853
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T14:15:48+00:00

MacGDBp has a setting called Break on first line of execution, which I turned

  • 0

MacGDBp has a setting called “Break on first line of execution”, which I turned off.. but it doesn’t seem to do anything. It still catches and breaks every single query, making it a useless app to use.

Does anyone use MacGDBp that knows a way around this? I’d love to make use of it, but at this point it’s not worth it.

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I realize that this could be much more involved, but that sounds like what happens when you step through the code.

    Which button are you clicking? The Continue button should jump to the next breakpoint.

    I grabbed this from:
    Debugging your PHP Code: XDebug on MAMP with TextMate and MacGDBp Support

    xdebug macgdbp buttons

    From left to right, the buttons are:

    Step into: Clicking this will advance the debugger one step and, if necessary, go “into” the function, class, file, etc. By clicking this button repeatedly, you can step through every part of the process.

    Step out: This will move up a level. For example, if you are mid-way through a function and you step out, the debugger will advance to the next part of the code, skipping the remainder of the function.

    Step Over (Skip): This will skip examining the next step. For example, if the current line is pointing to a function, and you do not want to see the function execute, you can skip it with this button. Clicking this will simply advance to the next line in the current scope.

    Continue (Play): Continue execution until either the next breakpoint or the end of the script.

    Reset: Remove the current debugging session and wait for the next request from the server.

    Using these buttons, you can navigate through the execution of a script. While this will give you a detailed step-by-step analysis of a program as it executes, it can often be overkill. More often, you will want to analyze just a small part of your script. That is best accomplished with breakpoints.

    A breakpoint is a marker that tells the debugger to pause when the location is reached. Using breakpoints, you can set the debugger to play through most of the code, pausing only when it gets to the portion of interest.

    EDIT: February 26, 2012

    Hi Naatan,

    You could take a look at the xdebug logs by adding this line to your php.ini file:

    xdebug.remote_log=/var/log/xdebug/xdebug.log

    You can determine if MacGDBp is sending any breakpoints and if it’s sending a run command or a step_into command.

    Here is what I see for six different scenarios. I stripped out most of the data as it took a lot of space, let me know if you need to see data for a specific line.

    1) “BREAK ON FIRST LINE OF EXECUTION” = OFF AND NO BREAKPOINTS

    Log opened at 2012-02-26 22:27:47
-> <init

<- feature_set -i 2859 -n show_hidden -v 1
-> <response

<- feature_set -i 2860 -n max_depth -v 3
-> <response

<- feature_set -i 2861 -n max_children -v 30
-> <response

<- feature_get -i 2862 -n max_data
-> <response

<- eval -i 2863 --
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="eval" transaction_id="2863"><property address=

<- run -i 2864
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="2864" status="stopping" reason="ok"></response>

    2) “BREAK ON FIRST LINE OF EXECUTION” = ON AND NO BREAKPOINTS

      Log opened at 2012-02-26 22:35:39
  -> <init

  <- feature_set -i 2913 -n show_hidden -v 1
  -> <response

  <- feature_set -i 2914 -n max_depth -v 3
  -> <response

  <- feature_set -i 2915 -n max_children -v 30
  -> <response

  <- feature_get -i 2916 -n max_data
  -> <response

  <- eval -i 2917 --
  -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="eval" transaction_id="2917"><property address=

  // 2a) STEP INTO CALLED BECAUSE "BREAK ON FIRST LINE OF EXECUTION" IS TURNED ON
  <- step_into -i 2918
  -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="step_into" transaction_id="2918" status="break" reason="ok"><xdebug:message filename="file:///var/www/application/html/index.php" lineno="2"></xdebug:message></response>

  <- stack_get -i 2919
  -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="2919"><stack where="{main}" level="0" type="file" filename="file:///var/www/application/html/index.php" lineno="2"></stack></response>

  <- context_names -i 2920
  -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="2920"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context></response>

  <- context_get -i 2921 -c 0
  -> <response xmlns= // SHOWS "Locals" VARIABLES

  <- context_get -i 2922 -c 1
  -> <response xmlns= // SHOWS "Superglobals" VARIABLES

  // 2b) CLICK CONTINUE
  <- run -i 2923
  -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="2923" status="stopping" reason="ok"></response>

    3) “BREAK ON FIRST LINE OF EXECUTION” = ON, WITH BREAKPOINT ON FIRST LINE

    Log opened at 2012-02-26 22:41:56
-> <init

<- feature_set -i 2936 -n show_hidden -v 1
-> <response

<- feature_set -i 2937 -n max_depth -v 3
-> <response

<- feature_set -i 2938 -n max_children -v 30
-> <response

<- feature_get -i 2939 -n max_data
-> <response

// 3a) LISTS ALL BREAKPOINTS THAT ARE SET
<- breakpoint_set -i 2940 -t line -s enabled -f file:///var/www/application/html/index.php -n 2
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="2940" state="enabled" id="179940003"></response>

<- eval -i 2941 --
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="eval" transaction_id="2941"><property address=

// 3b) STEP INTO CALLED BECAUSE "BREAK ON FIRST LINE OF EXECUTION" = ON
<- step_into -i 2942
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="step_into" transaction_id="2942" status="break" reason="ok"><xdebug:message filename="file:///var/www/application/html/index.php" lineno="2"></xdebug:message></response>

<- stack_get -i 2943
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="2943"><stack where="{main}" level="0" type="file" filename="file:///var/www/application/html/index.php" lineno="2"></stack></response>

<- context_names -i 2944
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="2944"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context></response>

<- context_get -i 2945 -c 0
-> <response xmlns= // SHOWS "Locals" VARIABLES

<- context_get -i 2946 -c 1
-> <response xmlns= // SHOWS "Superglobals" VARIABLES

// 3c) CLICK CONTINUE
<- run -i 2947
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="2949" status="stopping" reason="ok"></response>

    4) “BREAK ON FIRST LINE OF EXECUTION” = ON, WITH BREAKPOINT ON LINE 10

    Log opened at 2012-02-27 00:29:26
-> <init

<- feature_set -i 3023 -n show_hidden -v 1
-> <response

<- feature_set -i 3024 -n max_depth -v 3
-> <response

<- feature_set -i 3025 -n max_children -v 30
-> <response

<- feature_get -i 3026 -n max_data
-> <response

// 4a) LISTS ALL BREAKPOINTS THAT ARE SET
<- breakpoint_set -i 3027 -t line -s enabled -f file:///var/www/application/html/index.php -n 10
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="3027" state="enabled" id="180020001"></response>

<- eval -i 3028 --
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="eval" transaction_id="3028"><property address=

// 4b) STEP INTO CALLED BECAUSE "BREAK ON FIRST LINE OF EXECUTION" = ON
<- step_into -i 3029
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="step_into" transaction_id="3029" status="break" reason="ok"><xdebug:message filename="file:///var/www/application/html/index.php" lineno="2"></xdebug:message></response>

<- stack_get -i 3030
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="3030"><stack where="{main}" level="0" type="file" filename="file:///var/www/application/html/index.php" lineno="2"></stack></response>

<- context_names -i 3031
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="3031"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context></response>

<- context_get -i 3032 -c 0
-> <response xmlns= // SHOWS "Locals" VARIABLES

<- context_get -i 3033 -c 1
  -> <response xmlns= // SHOWS "Superglobals" VARIABLES

// 4c) CLICK CONTINUE - GOES TO BREAKPOINT ON LINE 10
<- run -i 3034
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="3034" status="break" reason="ok"><xdebug:message filename="file:///var/www/application/html/index.php" lineno="10"></xdebug:message></response>

<- stack_get -i 3035
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="3035"><stack where="{main}" level="0" type="file" filename="file:///var/www/application/html/index.php" lineno="10"></stack></response>

<- context_names -i 3036
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="3036"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context></response>

<- context_get -i 3037 -c 0
-> <response xmlns= // SHOWS "Locals" VARIABLES

<- context_get -i 3038 -c 1
  -> <response xmlns= // SHOWS "Superglobals" VARIABLES

// 4d) CLICK CONTINUE
<- run -i 3039
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="2864" status="stopping" reason="ok"></response>

    5) “BREAK ON FIRST LINE OF EXECUTION” = OFF, WITH BREAKPOINT ON FIRST LINE

    Log opened at 2012-02-26 22:49:46
-> <init

<- feature_set -i 2962 -n show_hidden -v 1
-> <response

<- feature_set -i 2963 -n max_depth -v 3
-> <response

<- feature_set -i 2964 -n max_children -v 30
-> <response

<- feature_get -i 2965 -n max_data
-> <response

// 5a) LISTS ALL BREAKPOINTS THAT ARE SET
<- breakpoint_set -i 2966 -t line -s enabled -f file:///var/www/application/html/index.php -n 2
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="2966" state="enabled" id="180160005"></response>

<- eval -i 2967 --
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="eval" transaction_id="2967"><property address="140734566267920" type="string" size="77" encoding="base64"><![CDATA[aHR0cDovL2RldmVsb3BtZW50Lm1hcmluYXMuY29tL2luZGV4LnBocD9YREVCVUdfU0VTU0lPTl9TVEFSVD1uZXRiZWFucy14ZGVidWc=]]></property></response>

<- run -i 2968
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="2968" status="break" reason="ok"><xdebug:message filename="file:///var/www/application/html/index.php" lineno="2"></xdebug:message></response>

<- stack_get -i 2969
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="2969"><stack where="{main}" level="0" type="file" filename="file:///var/www/application/html/index.php" lineno="2"></stack></response>

<- context_names -i 2970
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="2970"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context></response>

<- context_get -i 2971 -c 0
-> <response xmlns= // SHOWS "Locals" VARIABLES

<- context_get -i 2972 -c 1
-> <response xmlns= // SHOWS "Superglobals" VARIABLES

// 5b) CLICK CONTINUE
<- run -i 2973
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="2973" status="stopping" reason="ok"></response>

    6) “BREAK ON FIRST LINE OF EXECUTION” = OFF, WITH BREAKPOINT ON LINE 10

    Log opened at 2012-02-27 00:46:23
-> <init

<- feature_set -i 3052 -n show_hidden -v 1
-> <response

<- feature_set -i 3053 -n max_depth -v 3
-> <response

<- feature_set -i 3054 -n max_children -v 30
-> <response

<- feature_get -i 3055 -n max_data
-> <response

// 6a) LISTS ALL BREAKPOINTS THAT ARE SET
<- breakpoint_set -i 3056 -t line -s enabled -f file:///var/www/application/html/index.php -n 10
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="3056" state="enabled" id="179990006"></response>

<- eval -i 3057 --
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="eval" transaction_id="3057"><property address="140734566267920" type="string" size="77" encoding="base64"><![CDATA[aHR0cDovL2RldmVsb3BtZW50Lm1hcmluYXMuY29tL2luZGV4LnBocD9YREVCVUdfU0VTU0lPTl9TVEFSVD1uZXRiZWFucy14ZGVidWc=]]></property></response>

<- run -i 3058
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="3058" status="break" reason="ok"><xdebug:message filename="file:///var/www/application/html/index.php" lineno="10"></xdebug:message></response>

<- stack_get -i 3059
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stack_get" transaction_id="3059"><stack where="{main}" level="0" type="file" filename="file:///var/www/application/html/index.php" lineno="10"></stack></response>

<- context_names -i 3060
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="context_names" transaction_id="3060"><context name="Locals" id="0"></context><context name="Superglobals" id="1"></context></response>

<- context_get -i 3061 -c 0
-> <response xmlns= // SHOWS "Locals" VARIABLES

<- context_get -i 3062 -c 1
-> <response xmlns= // SHOWS "Superglobals" VARIABLES

// 6b) CLICK CONTINUE
<- run -i 3063
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run" transaction_id="3063" status="stopping" reason="ok"></response>

    Be Well,
    Joe

    • 0