-
Notifications
You must be signed in to change notification settings - Fork 261
[Errno 14] Bad address; Error occurs when run python include numpy. #838
Comments
Can you run it with |
Error message with
All of error message is in ErrorMessage.txt. |
Looking at this log, the actual error happens during this:
Since stream Looks like a legit bug. If we'll have time, we will look into this. Thanks for reporting. |
I run code under non-SGX Graphene(maybe Debug messages are in non-SGX Graphene debug.txt. Sorry to trouble you, but I look forward to check and fix it as soon as possible... |
@dimakuv Any Updates on this?? |
@kanakraju73 @diwata11 This was fixed on the latest (master branch) Graphene. I just tested it (in particular, the script and manifest attached in
By the way, there is no need for this line in the manifest:
This is because Graphene emulates |
Thanks for checking! Could you tell me the solution if possible? ( ERROR messages are in ERRORs_20190819.txt. ) |
I've also tested with the latest master branch and end up with the same error. With SGX Without SGX |
@dimakuv seems like you forgot to attach Codes.zip file. Can you upload it now? |
Unfortunately I have no time currently to verify this again. It worked on my Ubuntu 16.04 though... |
@diwata11 @kanakraju73 I'm cleaning up old issues right now. Does this issue reproduce on current master? |
No response from the reporters and we couldn't reproduce the issue, closing. It's probably already fixed on master. |
The source code is quite simple(the same as #709), it can be performed when be running without SGX.
When I run the python code above, [Errno 14] error message occurs like this(some code masks like "xxx").:
I think that the cause of this error is urandom function, so I check it using following code.
When I run the python code above, error message is as follows.
What is the root cause of this problem?
I know that you are very busy, but I would appreciate it very much if you could advise me.
※ Codes above and manifest are in Codes.zip.
The text was updated successfully, but these errors were encountered: