Re: EXC_BAD_ACCESS in torrent_handle::get_peer_info

Hi Arvid,

thank you for the suggestion - disabling Geo_IP and Resolve_Countries
did the trick :)

As I wrote in the first mail, I am using the 0.16 release. In fact, I
did get the linking error you mentioned (right after upgrading from
0.15.8), even though I've never set any of the TORRENT_DISABLE* flags
before. After one very frustrating hour of debugging, I tried out
disabling DHT on both sides and got the linking working again. *GEO_IP
and *RESOLVE_COUNTRIES are flags that I'm also not interested in, so
this makes it really weird.. Anyhow, thanks for the advice, I'm glad
to have it up and running again :)

Best,
Alex

On Tue, May 1, 2012 at 6:59 PM,  <arvid <at> cs.umu.se> wrote:
> Quoting Alex Shterev <cold.phusion <at> gmail.com>:
>
>> Hi guys,
>>
>> I'm building a GUI BitTorrent client with libtorrent and I'm trying to
>> visualize some information about the connected peers, such as IP,
>> upload/download speed, etc. So far I've been trying to use
>> torrent_handle::get_peer_info, but I keep getting an EXC_BAD_ACCESS
>> at:
>
> This typically happen if you build libtorrent with a different set of TORRENT*
> defines than you define when you use it.
>
> I'm guessing it's either TORRENT_DISABLE_GEO_IP or
> TORRENT_DISABLE_RESOLVE_COUNTRIES that differs to cause this.
>
> Which version of libtorrent are you using? there's a feature in 0.16 that's
> supposed to give you a link error in this case.
>
> --
> Arvid Norberg

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/