Вивчайте Debugging Strategies | Logging, Debugging, and Production Strategies

Debugging is an essential part of PHP development, especially when you need to identify the cause and location of errors in your application. PHP provides several built-in tools to help you trace the flow of your program and collect valuable information when things go wrong. Among the most useful are stack traces, the debug_backtrace function, and contextual logging. A stack trace shows the sequence of function calls that led to an error, making it easier to pinpoint where a problem originated. The debug_backtrace function allows you to programmatically inspect the call stack, while contextual logging involves recording extra information—such as variable values or user actions—at the time of an error. Using these tools together gives you a clear picture of what happened in your code and why.

index.php


              1234567891011121314151617181920212223242526272829303132333435363738
            
<?php

function thirdLevel() {
    throw new Exception("Something went wrong in thirdLevel!");
}

function secondLevel() {
    thirdLevel();
}

function firstLevel() {
    secondLevel();
}

try {
    firstLevel();
} catch (Exception $e) {
    // Output stack trace using Exception's getTraceAsString
    echo "Exception caught:\n";
    echo $e->getMessage() . "\n\n";
    echo "Stack trace from Exception:\n";
    echo $e->getTraceAsString() . "\n\n";
    
    // Output stack trace using debug_backtrace
    echo "Stack trace from debug_backtrace:\n";
    foreach (debug_backtrace() as $trace) {
        if (isset($trace['file'])) {
            echo "File: {$trace['file']} ";
        }
        if (isset($trace['line'])) {
            echo "Line: {$trace['line']} ";
        }
        if (isset($trace['function'])) {
            echo "Function: {$trace['function']} ";
        }
        echo "\n";
    }
}

The example above demonstrates how to use PHP's debugging tools to diagnose errors. When the thirdLevel function throws an exception, the catch block captures it and prints both the stack trace from the exception object and the output of debug_backtrace. The stack trace from getTraceAsString shows the sequence of function calls that led to the error, including file names and line numbers. This helps you quickly identify where in your code the problem started and how execution reached that point. The debug_backtrace function provides similar information in a programmatic format, which you can use for custom logging or more advanced debugging. By examining these traces, you gain insight into the exact flow of your application, making it much easier to find and fix bugs. Contextual logging—such as recording variable values or user actions at each step—can further enhance your ability to understand what happened, especially in complex applications.

Все було зрозуміло?

Дякуємо за ваш відгук!

Секція 3. Розділ 3

Запитати АІ

Запитайте про що завгодно або спробуйте одне із запропонованих запитань, щоб почати наш чат

Свайпніть щоб показати меню

index.php


              1234567891011121314151617181920212223242526272829303132333435363738
            
<?php

function thirdLevel() {
    throw new Exception("Something went wrong in thirdLevel!");
}

function secondLevel() {
    thirdLevel();
}

function firstLevel() {
    secondLevel();
}

try {
    firstLevel();
} catch (Exception $e) {
    // Output stack trace using Exception's getTraceAsString
    echo "Exception caught:\n";
    echo $e->getMessage() . "\n\n";
    echo "Stack trace from Exception:\n";
    echo $e->getTraceAsString() . "\n\n";
    
    // Output stack trace using debug_backtrace
    echo "Stack trace from debug_backtrace:\n";
    foreach (debug_backtrace() as $trace) {
        if (isset($trace['file'])) {
            echo "File: {$trace['file']} ";
        }
        if (isset($trace['line'])) {
            echo "Line: {$trace['line']} ";
        }
        if (isset($trace['function'])) {
            echo "Function: {$trace['function']} ";
        }
        echo "\n";
    }
}

Все було зрозуміло?

Дякуємо за ваш відгук!

Секція 3. Розділ 3