Re: [Boost-bugs] [Boost C++ Libraries] #2555: SIGTRAP received while calling a wrapped function with ""

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2555: SIGTRAP received while calling a wrapped function with ""
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-12-02 14:05:50

#2555: SIGTRAP received while calling a wrapped function with ""
-------------------------------------------------+--------------------------
  Reporter:  bruno dot lalande at gmail dot com  |       Owner:  dave   
      Type:  Bugs                                |      Status:  closed 
 Milestone:  Boost 1.38.0                        |   Component:  Python 
   Version:  Boost 1.36.0                        |    Severity:  Problem
Resolution:  invalid                             |    Keywords:         
-------------------------------------------------+--------------------------

Comment(by anonymous):

 Indeed, those informations were missing, sorry for that.

 Here is where the different things come from:
  * python is the precompiled official package
  * gcc and gdb are the precompiled packages provided by the mingw project
  * boost has been built using: bjam -g --v2 --toolset=gcc --mno-cygwin
 --with-python python-debugging=on variant=debug threading=single
 link=shared
  * bjam is the 3.1.16 precompiled binary provided by Boost
  * the mymodule module has been compiled using: g++ -Wall -O0 -DBUILD_DLL
 -g -DBOOST_DEBUG_PYTHON -IC:\Python22\include -LC:\Python22\libs (+ the -I
 and -L options to our compiled Boost.Python)

 You will find in the new attachment a trace that shows some Boost.Python
 debug informations. We begin by placing a pending breakpoint on foo, then
 we import mymodule. We first call the foo() function with a non-empty
 string, which works well. Then we do the same but with an empty string,
 which results in a SIGTRAP raised while we are in
 python/detail/caller.hpp:225.

 We know the stability of Boost.Python, that we heavily use. The point is
 that this problem can occur under this form only in gdb, as "SIGTRAP is
 the signal thrown by computer programs when a condition arises that a
 debugger has requested to be informed of" (according to wikipedia). So it
 won't arise in a normal run, but the potential problem it shows can have
 another consequence later. That's why we thought it could be useful to
 report it here. This being said, it's very difficult to make sure it's not
 a gdb bug. We are open to any suggestion of test that could be done to
 clarify things.

 Bruno

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/2555#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.