Re: [gtk-gnutella-devel] Odd assertion failure in iso3166.c

2009-11-04 Thread Raphael Manfredi
Quoting Matthew Lye from ml.softs.gtk-gnutella.devel: :So that explains the assertion failure, at least. Indeed. In r17182 I have added an assertion to check that the server's country code remains valid at all times. This is by no means a fix, but a starting point to see at which time things ge

Re: [gtk-gnutella-devel] Odd assertion failure in iso3166.c

2009-11-03 Thread Raphael Manfredi
Quoting Matthew Lye from ml.softs.gtk-gnutella.devel: :in frame 5: :row = 0, :i = 1, and :{struct download}key = {magic = DOWNLOAD_MAGIC, src_handle = :2434507541, src_handle_valid = 1, : error_str = "Requeued due to timeout at 10:41:53 - rescheduled for :10:42:13 #1\00037:43 #0", '\0' , sta

Re: [gtk-gnutella-devel] Odd assertion failure in iso3166.c

2009-11-03 Thread Raphael Manfredi
Quoting Matthew Lye from ml.softs.gtk-gnutella.devel: :Hey all, : :I have encountered a crash that I find rather perplexing, seemingly in :iso3166.c: : :> #2 0x001e93d8 in assertion_failure (data= unavailable, due to optimizations>) at fast_assert.c:104 :> #3 0x001fbfc4 in iso3166_country_cc (

Re: [gtk-gnutella-devel] Odd assertion failure in iso3166.c

2009-11-03 Thread Bill Pringlemeir
On 3 Nov 2009, m...@talkwireless.ca wrote: > Hey all, > > I have encountered a crash that I find rather perplexing, seemingly in > iso3166.c: I have had preplexing problems as well with stack traces. I find this method gives the best stack traces with '-02' (which will be the default). ./gtk-g

Re: [gtk-gnutella-devel] Odd assertion failure in iso3166.c

2009-11-03 Thread Matthew Lye
On 3-Nov-09, at 5:31 PM, Raphael Manfredi wrote: > Quoting Matthew Lye from ml.softs.gtk- > gnutella.devel: > :in frame 5: > :row = 0, > :i = 1, and > :{struct download}key = {magic = DOWNLOAD_MAGIC, src_handle = > :2434507541, src_handle_valid = 1, > : error_str = "Requeued due to timeout at

[gtk-gnutella-devel] Odd assertion failure in iso3166.c

2009-11-03 Thread Matthew Lye
Hey all, I have encountered a crash that I find rather perplexing, seemingly in iso3166.c: > #0 0x93a0ab50 in __kill () > #1 0x93aa5c00 in abort () > #2 0x001e93d8 in assertion_failure (data= unavailable, due to optimizations>) at fast_assert.c:104 > #3 0x001fbfc4 in iso3166_country_cc (cod