I've heard rumours about this before, but it would really help if you could provide a small reproducible (set of) tests. I don't think it would need all of Symfony to reproduce this.

That said, I am not sure whether I will be able to detect this behaviour well enough to do anything about it, as things like shutdown or exception handlers sort of run in the same script's context, but also sideways of it.

Hi?

Did you manage to make a reproducible case?

cheers,
Derick

Just download fresh symfony (I checked now on 4.2 https://symfony.com/download. And run main controller in profile mode.

You will see two profile files. One correct for index.php second (broken) for ErrorHandler.php

Hi — I know nothing about Symfony. Can you please explain in detail, with the exact steps on how to do " And run main controller in profile mode.".

cheers,
Derick

Hi - could you please point me to the answer to my Symfony question please?

Hi Derick,

I think this could be related to 0001589 because he mentioned that the "second haven't correct names/paths".
Testcase with sample output is attached.
When you profile "xdtest1.php" two profiler output files will be created, one for the main "xdtest1.php" and a second one for the error/exception handler.

In the second file all file and function names will be missing when these first appeared in the first file:
"fl=(1) php:internal"
"fl=(2) /Users/asoki/develop/server/apps/apache/htdocs/xdtest1-errhandler.php"
"fn=(4) php::rand"

OS: MacOS 10.14.3

the configuration was:
[xdebug]
xdebug.profiler_enable=1
xdebug.profiler_output_dir=/Users/asoki/develop/server/tmp
xdebug.profiler_output_name=cachegrind.out.%p.%t
xdebug.profiler_aggregate=0
xdebug.profiler_append=0
xdebug.profiler_enable_trigger=0
xdebug.profiler_enable_trigger_value="foobar"

Thanks @asoki, I can indeed reproduce this with your minimal test case.