Environment Information:
Running on Windows 11 with WSL2. The source code resides on the Windows file system, while PHP and Nginx are installed on an Ubuntu 22.04 image within WSL2.

Issue: After upgrading Xdebug from version 3.2.1 to 3.4.2, certain files no longer hit breakpoints as expected. This problem did not occur in earlier versions of Xdebug—specifically, everything up to and including 3.3.0alpha2 functioned correctly. However, this behaviour changed starting with version 3.3.0. As we're preparing to upgrade to PHP 8.4, resolving this issue is critical to moving forward.

For example, I have a file named dashboard.php that contains a class called Dashboard with a method named index(). In newer versions of Xdebug, if I set a breakpoint inside the index() method, it doesn't get hit. However, if I rename the file to Dashboard.php (matching the class name), the breakpoint works as expected. What change occurred in Xdebug that caused this behaviour to break and why does it work fine without having to rename the file in older versions?

I've attached logs demonstrating the issue: one from Xdebug 3.3.0alpha2 where the breakpoint is hit as expected, and another from Xdebug 3.4.2 where the same breakpoint fails to trigger.

While my simple example can easily be rectified we have a very large project and renaming all the files is not practical at this stage.