seems due to the new implemention of trait, not only debug_backtrace, I think the 
reflection is also affected.

dmitry, do you think this should be fixed?

thanks

Laruence, you are right. Reflection, debug_backtrace() and get_class_methods() are affected.

It would be good to fix it, however, I don't see a good way to do it, and I don't like to introduce a new hack. (e.g. resolving alias name by looking into hash table key).

Actually we have the same situation with class aliases.

In general, we can fix it in 5.5 using some inefficient way (e.g. add op_array->alias_function_name)

Any ideas are welcome.

yes, that alias name gave us too many pains :)...

add a new alias_name is a easy and clear way. 

thanks

Or please add magic constant, ie. __ALIASSED_METHOD__ or something (#61033)... The 
backtrace code is just workaround for me in this case.

Personally, I would remove traits at all :(
Of course, it's not a case, but we hardly ever going to introduce new trait related magic in 5.4.*

an idea is search the function in ce->function table to get the lowercase alias 
name, then search in ce->traits_aliases for the origin function name,

patch will be attached, but it will definitely slowdown the debug_backtrace.

I've added another patch (bug64239-2.patch), but it's incorrect anyway :(

Test script:
---------------
<?php
class A {
	public function test() {}
}
class B {
	use T2 { t2method as Bmethod; }
}
trait T2 {
	public function t2method() {
		debug_print_backtrace();
	}
}
$b = new B();
$b->t2method();
$b->Bmethod();

Expected result:
----------------
#0  B->t2method() called at [test.php:14]
#0  B->Bmethod() called at [test.php:15]

Actual result:
--------------
#0  B->Bmethod() called at [test.php:14]
#0  B->Bmethod() called at [test.php:15]

new patch attached, which fixed that issue you mentioned