|
0002357 |
502 error from nginx when debugging exited on signal 11 (SIGSEGV - core dumped) Step Debugging - 2025-06-23 15:27 |
|
0002356 |
The step debugging reproduce wrong output values Step Debugging - 2025-06-22 15:57 |
|
0002346 |
Add benchmarking tool Uncategorized - 2025-05-01 09:27 |
|
0002222 |
Xdebug holds a reference to objects in the stack trace of a caught exception Tracing - 2025-03-09 21:28 |
|
0002150 |
Collapse the two FOREACH start op codes into one to improve path/branch coverage accurateness Code Coverage - 2025-01-14 17:19 |
|
0002301 |
Feature Request: Add Option to Suppress Error "Could not connect to debugging client" Step Debugging - 2024-11-27 15:40 |
|
0002299 |
Apache OPTIONS dummy connection spams error.log with "Cannot load Xdebug - it was already loaded" Uncategorized - 2024-10-20 00:20 |
|
0002298 |
Add additional flamegraph format. Profiling - 2024-10-16 10:06 |
|
0002204 |
Ability to exclude paths from profiling Profiling - 2024-04-15 13:38 |
|
0002072 |
Rewrite the profiler Profiling - 2024-04-15 13:38 |
|
0002357 |
502 error from nginx when debugging exited on signal 11 (SIGSEGV - core dumped) Step Debugging - 2025-06-23 15:27 |
|
0002356 |
The step debugging reproduce wrong output values Step Debugging - 2025-06-22 15:57 |
|
0002350 |
Crash when a certain page generates an exception since Xdebug 3.4.3 Stacktraces - 2025-06-13 15:07 |
|
0002352 |
Crash when using latest Xdebug version when throwing exceptions Stacktraces - 2025-06-12 11:51 |
|
0002349 |
Regression in Xdebug 3.4.3 breaks throwing exceptions in nested generators Stacktraces - 2025-06-12 11:50 |
|
0002354 |
The __invoke frame in call stacks don't have the argument name in the trace Stacktraces - 2025-06-12 11:46 |
