Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Erlang Programming
Home
+ new post
About this group
Join this group
enif_send and non-SMP issues (enif_send: env==NULL on non-SMP VMAborted)
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Anatoly Kanivetskiy  
View profile  
 More options Oct 11 2012, 6:41 pm
From: Anatoly Kanivetskiy <chaos.a....@gmail.com>
Date: Thu, 11 Oct 2012 15:41:33 -0700 (PDT)
Local: Thurs, Oct 11 2012 6:41 pm
Subject: [erlang-questions] enif_send and non-SMP issues (enif_send: env==NULL on non-SMP VMAborted)
Print | Individual message | Show original | Report this message | Find messages by this author

Hello, sirs!

Recently, under some dramatic circumstances, I have discovered that NIF's
are doomed to brutal termination, when enif_send is called from spawned
threads.
It forces me to just throw an exception during NIF initialization process,
whenever erlang:system_info(smp_support) returns false.
As I understood, there is no general solution for this problem, and it can
be tricky to gracefully handle this, since usually it forces you to think
about two threading modes of your NIF at the same time.

So, the question to erlang masters: what will be your advice to all
developers, which once will find that their nif's are not more
cpu-topology-agnostic, and their applications fails to run on single-core
environments?

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google