Cleanup shutdown, enable proper memory leak displaying2015-07-24T15:17:26+00:00Bob Weinandbobwei9@hotmail.com2015-07-24T15:17:09+00:0013525328ede9db6f8235b4e7f91f7bce80235880
phpdbg should not memory leak...
phpdbg should not memory leak...
Fix misbehaviors with uncaught exceptions and finally or eval2015-07-20T16:00:43+00:00Bob Weinandbobwei9@hotmail.com2015-07-20T15:52:57+00:0075a3de0cd8b79e2f813eaa663d90bb57edc7a146
Switch asprintf to spprintf in phpdbg opcode dump2015-07-17T14:53:07+00:00Nikita Popovnikic@php.net2015-07-17T14:49:34+00:0020e5027293bf8711bc4f6cabd8f304ca5b127690
Also use %td where appropriate, a lot of the values are ptrdiff
based.
Fix a leak in phpdbg_frame.c.
Also use %td where appropriate, a lot of the values are ptrdiff
based.
Fix a leak in phpdbg_frame.c.
Use ZSTR_ API to access zend_string elements (this is just renaming without semantick changes).2015-06-30T10:59:27+00:00Dmitry Stogovdmitry@zend.com2015-06-30T10:59:27+00:007aa7627172c11979ec45c2db85f99182812ee59d
Make backtraces *much* more readable2015-06-29T00:51:10+00:00Bob Weinandbobwei9@hotmail.com2015-06-29T00:51:10+00:00088f589f7d5aa24a8c42fea582dc53b8cb7232c2
Fix phpdbg class fetch / method opcodes2015-05-26T22:55:26+00:00Bob Weinandbobwei9@hotmail.com2015-05-26T22:55:15+00:005bec1490f90e1061d4b3416c8e34a5369c616475
Also consider specific catches when checking for uncaught2015-04-21T23:08:08+00:00Bob Weinandbobwei9@hotmail.com2015-04-21T23:07:52+00:00e09a0bfc9e849b558fb03be33ac463ef3288305b
Break on uncaught exceptions in current frame in phpdbg2015-04-21T23:08:07+00:00Bob Weinandbobwei9@hotmail.com2015-04-21T21:09:09+00:0073d31d44e8b59804077b4f6451e06caf69166a6b