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
Handling exceptions in nodejs addon
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
  2 messages - 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
 
Sergey Volvovski  
View profile  
 More options Oct 9 2012, 3:16 pm
From: Sergey Volvovski <svolvo2...@gmail.com>
Date: Tue, 9 Oct 2012 12:16:37 -0700 (PDT)
Local: Tues, Oct 9 2012 3:16 pm
Subject: Handling exceptions in nodejs addon

I just started using nodejs and currently I'm working on addon that is
supposed to use the other library. Those library is using internally
boost::asio. When I'm trying to compile my addon code I receive the
following output:

In file included from
/usr/local/boost_1_51_0/boost/asio/detail/impl/throw_error.ipp:21:0,
                 from
/usr/local/boost_1_51_0/boost/asio/detail/throw_error.hpp:52,
                 from
/usr/local/boost_1_51_0/boost/asio/detail/impl/posix_mutex.ipp:23,
                 from
/usr/local/boost_1_51_0/boost/asio/detail/posix_mutex.hpp:73,
                 from
/usr/local/boost_1_51_0/boost/asio/detail/mutex.hpp:25,
                 from
/usr/local/boost_1_51_0/boost/asio/detail/service_registry.hpp:20,
                 from
/usr/local/boost_1_51_0/boost/asio/impl/io_service.hpp:19,
                 from /usr/local/boost_1_51_0/boost/asio/io_service.hpp:767,
                 from
/usr/local/boost_1_51_0/boost/asio/basic_io_object.hpp:19,
                 from
/usr/local/boost_1_51_0/boost/asio/basic_socket.hpp:19,
                 from
/usr/local/boost_1_51_0/boost/asio/basic_datagram_socket.hpp:20,
                 ............

/usr/local/boost_1_51_0/boost/system/system_error.hpp: In member function
‘virtual const char* boost::system::system_error::what()
const’:/usr/local/boost_1_51_0/boost/system/system_error.hpp:70:16: error:
exception handling disabled, use -fexceptions to enable

However adding -fexceptions to cflags section of my binding.gyp does not
have any effect, I still have the same output.
Is there any work-around for this problem?

Any kind of help is appreciated.

Thanks,
Sergey


 
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.
Ben Noordhuis  
View profile  
 More options Oct 9 2012, 7:48 pm
From: Ben Noordhuis <i...@bnoordhuis.nl>
Date: Wed, 10 Oct 2012 01:48:34 +0200
Local: Tues, Oct 9 2012 7:48 pm
Subject: Re: [nodejs] Handling exceptions in nodejs addon

Use BOOST_NO_EXCEPTIONS. Mixing -fexceptions and -fno-exceptions code
(node, v8) is a bad idea unless you're really, really sure that you
keep all exceptions contained.

 
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     Older topic »