[issue27462] NULL Pointer deref in binary_iop1 function

2016-07-07 Thread Emin Ghuliev
Changes by Emin Ghuliev : -- resolution: not a bug -> wont fix status: pending -> closed ___ Python tracker ___

[issue27462] NULL Pointer deref in binary_iop1 function

2016-07-07 Thread R. David Murray
R. David Murray added the comment: Well, unless you can find a way to reproduce it with python code, it isn't interesting to us. -- resolution: -> not a bug status: open -> pending ___ Python tracker

[issue27462] NULL Pointer deref in binary_iop1 function

2016-07-07 Thread Emin Ghuliev
Emin Ghuliev added the comment: Nope, invalid bytecode file generated by fuzzer for the purpose of bug researching. Just python doesn't determine whether a variable is empty or valid. -- ___ Python tracker

[issue27462] NULL Pointer deref in binary_iop1 function

2016-07-07 Thread R. David Murray
R. David Murray added the comment: Are you saying python generated an invalid bytecode file? -- nosy: +r.david.murray ___ Python tracker ___

[issue27462] NULL Pointer deref in binary_iop1 function

2016-07-07 Thread Emin Ghuliev
New submission from Emin Ghuliev: Python VM parses "0x3b" opcode (INPLACE_MODULO) in the bytecode file. Subsequently VM parses left and right arguments of the opcode (0x3b). If left and right arguments doesn't exists in the bytecode file that causes a segmentation fault. Which triggered by