Hey:
On Sat, Jan 2, 2016 at 7:59 PM, Derick Rethans wrote:
> On Thu, 31 Dec 2015, Nikita Popov wrote:
>
> > On Thu, Dec 31, 2015 at 1:09 AM, Derick Rethans wrote:
> >
> > > On Thu, 31 Dec 2015, Nikita Popov wrote:
> > >
> > > > For PHP 7 only: FAST_CALL always jumps to op1. op2 is not a jmp
>
On Thu, 31 Dec 2015, Nikita Popov wrote:
> On Thu, Dec 31, 2015 at 1:09 AM, Derick Rethans wrote:
>
> > On Thu, 31 Dec 2015, Nikita Popov wrote:
> >
> > > For PHP 7 only: FAST_CALL always jumps to op1. op2 is not a jmp
> > > addr, it's a try_catch_array offset. For FAST_RET there are no
> > >
On Thu, Dec 31, 2015 at 1:09 AM, Derick Rethans wrote:
> Hi!
>
> On Thu, 31 Dec 2015, Nikita Popov wrote:
>
> > On Wed, Dec 30, 2015 at 8:55 PM, Derick Rethans wrote:
> >
> > > While investigating an issue with Xdebug and fast_call/fast_ret, I
> > > noticed that the opcodes "associated" with the
Hi!
On Thu, 31 Dec 2015, Nikita Popov wrote:
> On Wed, Dec 30, 2015 at 8:55 PM, Derick Rethans wrote:
>
> > While investigating an issue with Xdebug and fast_call/fast_ret, I
> > noticed that the opcodes "associated" with the "finally" statement, are
> > rolled up in the previous line.
> > T
On Wed, Dec 30, 2015 at 8:55 PM, Derick Rethans wrote:
> Hi!
>
> While investigating an issue with Xdebug and fast_call/fast_ret, I
> noticed that the opcodes "associated" with the "finally" statement, are
> rolled up in the previous line.
>
> The code:
>
> 12 function extractFile()
> 3 {