DSWifi weird behavior with libcurl [solved]

[Jens]

I'm in the midst of a very long debug session trying to figure out why my Wi-Fi implementation isn't working. I'm using libcurl to commnicate with a web-server and suddenly "connect" just stops working. Even worse, if I try to log stuff to disk, it surprisingly stops logging before I'm getting to the part where it doesn't work. I thought it was due to file-system flushing and stuff, but I've finally ruled that out. Another hint was that when I do loading of assets in nitro between connects, it can suddenly crash trying to read the file. Therefor I'm suspecting some memory overwrite or some other low-level problem. This has been the case since I implemented the stuff a year ago (yeah, I know, slow progress), so I've gone through multiple revision of libnds, dswifi and libcurl. I'll continue digging, but debugging is obviously painful (printf to screen still works! . I was just curios to hear if anyone encountered anything like this.

[Jens]

As usual. After spending 2 days trying to debug this, I finally asked for some help here. Then 1 hour later I got it solved myself. It turns out that I had libcurl configurated in a way so that closesocket() wasn't called. Wasn't sure why this caused all the weird behavior, but things worked much better once that got called properly.

EDIT: For other people interested in using libcurl you can find my configuration file here http://www.collectingsmiles.com/temp/config-nds.h