-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault in PyVex #2
Comments
Alright, so I it looks like this is caused by a NULL expdHi. I pushed a fix On Mon, Nov 4, 2013 at 3:56 PM, Nilo Redini notifications@github.comwrote:
|
Ok, I cannot pull anything from here, I'll let you know tomorrow morning. Thanks! Nilo Nilo Redini On 04/nov/2013, at 11:23 PM, Yan notifications@github.com wrote:
|
Merged your fix. Thanks! |
Here it is the backtrace:
#0 wrap_IRExpr (i=0x0) at pyvex/pyvex_irexpr.c:64
#1 0x00007ffff4a90155 in pyIRStmtCAS_get_expdHi (self=, closure=)
#2 0x00000000004bd718 in ?? ()
, argc=2, ubp_av=0x7fffffffe418,#3 0x00000000004c6d6a in _PyObject_GenericGetAttrWithDict ()
#4 0x00000000004662fe in PyEval_EvalFrameEx ()
#5 0x0000000000466a42 in PyEval_EvalFrameEx ()
#6 0x000000000057bd02 in PyEval_EvalCodeEx ()
#7 0x000000000057dcd0 in ?? ()
#8 0x00000000004bf2a6 in PyObject_Call ()
#9 0x00000000004a4b8a in ?? ()
#10 0x00000000004bf2a6 in PyObject_Call ()
#11 0x00000000004bf5a6 in PyEval_CallObjectWithKeywords ()
#12 0x00000000004ef31b in PyInstance_New ()
#13 0x00000000004bf2a6 in PyObject_Call ()
#14 0x00000000004668da in PyEval_EvalFrameEx ()
#15 0x0000000000466a42 in PyEval_EvalFrameEx ()
#16 0x000000000057bd02 in PyEval_EvalCodeEx ()
#17 0x000000000057de02 in ?? ()
#18 0x00000000004bf2a6 in PyObject_Call ()
#19 0x00000000004a4b8a in ?? ()
#20 0x00000000004bf2a6 in PyObject_Call ()
#21 0x00000000004bf5a6 in PyEval_CallObjectWithKeywords ()
#22 0x00000000004ef31b in PyInstance_New ()
#23 0x00000000004bf2a6 in PyObject_Call ()
#24 0x00000000004668da in PyEval_EvalFrameEx ()
#25 0x0000000000466a42 in PyEval_EvalFrameEx ()
#26 0x0000000000466a42 in PyEval_EvalFrameEx ()
#27 0x000000000057bd02 in PyEval_EvalCodeEx ()
#28 0x00000000004667f8 in PyEval_EvalFrameEx ()
#29 0x000000000057bd02 in PyEval_EvalCodeEx ()
#30 0x000000000057de02 in ?? ()
#31 0x00000000004bf2a6 in PyObject_Call ()
#32 0x0000000000467e60 in PyEval_EvalFrameEx ()
#33 0x000000000057bd02 in PyEval_EvalCodeEx ()
#34 0x00000000004667f8 in PyEval_EvalFrameEx ()
#35 0x0000000000466a42 in PyEval_EvalFrameEx ()
#36 0x0000000000466a42 in PyEval_EvalFrameEx ()
#37 0x0000000000466a42 in PyEval_EvalFrameEx ()
#38 0x0000000000466a42 in PyEval_EvalFrameEx ()
#39 0x0000000000466a42 in PyEval_EvalFrameEx ()
#40 0x0000000000466a42 in PyEval_EvalFrameEx ()
#41 0x0000000000466a42 in PyEval_EvalFrameEx ()
#42 0x000000000057bd02 in PyEval_EvalCodeEx ()
#43 0x000000000057c77d in PyRun_FileExFlags ()
#44 0x000000000057e4a1 in PyRun_SimpleFileExFlags ()
#45 0x0000000000512cfd in Py_Main ()
#46 0x00007ffff68cb76d in __libc_start_main (main=0x41ba20
#47 0x000000000041ba51 in _start ()
The fault is due to a null value:
// wrap functionality
60 PyObject *wrap_IRExpr(IRExpr *i)
61 {
62 PyTypeObject *t = NULL;
63
64 switch (i->tag)
65 {
(gdb) p i
$1 = (IRExpr *) 0x0
If you need my binary, contact me.
The text was updated successfully, but these errors were encountered: