[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] lwip crash inside do_writemore when used in iOS extensi

From: Sergio R. Caprile
Subject: Re: [lwip-users] lwip crash inside do_writemore when used in iOS extension
Date: Fri, 15 Apr 2016 10:43:57 -0300
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.7.2

> all the settings are default (like #define MEM_SIZE 1048576)

Well, that amount of memory is certainly not a default.
$ grep -R "MEM_SIZE " *
src/include/lwip/opt.h:#define MEM_SIZE                        1600
test/unit/lwipopts.h:#define MEM_SIZE                        16000

lwIP knows nothing about iOS or resource limitations in extensions. lwIP is a piece of code you tailor to your hardware (physical or virtual). You known how much memory you have, you set lwIP to use that memory. You have a port written by someone, you have a network driver written by someone, you have an application written by someone that uses a certain lwIP API. You should make sure that your port is behaving properly, not calling lwIP basic functions from different contexts. You should run a known to work application, from the contrib tree, to make sure the port and driver work OK. You should then check your app against that contrib tree code and read the docs, to make sure you are doing things right. You can post your code to discuss whether you are doing things right, that helps a lot.

You are getting assertions, that is because some expected condition is not occurring. You should be able to figure out which one, follow it, and determine whether your problem comes from.

I would certainly think that your problem is not lwIP related, but you are using mem_size_t in 32-bits and I don't know if that has been thoroughly tested. Anyway, chances are your problem is most likely not in lwIP.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]