Re: [libtorrent] Segmentation fault while checking alert value

[arvid <ar...@cs...>]

On 2015-01-24 08:57, Steve W wrote:
>  
> Hi
> 
> I’m on RC_1_0 and using the Python binding. If I run the original
> client.py and read a value of an alert, a Segmentation fault 11 is
> thrown. For instance, with the simple
> patch http://dpaste.com/1B77KNN it’d give a seg fault once the alert
> is picked up. I’ve also tested several other alert types, including
> piece_finished_alert, and all produced the same result. Is this a bug?

I don't get a segfault, I get this:

Traceback (most recent call last):
   File "client.py", line 354, in <module>
     main()
   File "client.py", line 297, in main
     print_download_queue(console, h.get_download_queue())
TypeError: No to_python (by-value) converter found for C++ type: 
std::__1::tuple<std::__1::basic_string<char, 
std::__1::char_traits<char>, std::__1::allocator<char> >, unsigned 
short>

I need to investigate why this is failing (and why it's trying to create 
a std::tuple instead of a boost::python::tuple)

-- 
Arvid Norberg