ftpd hangs after LIST command about lwip-ftpd

[toelke]

Hi Tom,

I would guess this comes from exhausted heap memory or exhausted TCP PCBs.

Could you check those?

Cheers,
Philipp

[TomMajor]

Hi Philipp,

thanks for the quick reply. From your name, are you by any chance German
and could we communicate German?

This is my first start with lwIP and porting and everything is much more
complicated than I thought, although I found an old ST application note
with code for lwIP 1.3.1. which I adapted for my board (without an OS
first).

So my knowldege of lwIP is very limited, how would I check heap memory
or TCP PCB in the debugger?

This first test on the MCBSTM32C did run ok and this was the project I
wanted to try ftp on.

In the meantime, I tried to merge this into an existing uCOS-III project
(which is the final goal) but now I get a hardfault everytime I try to
access the web server. If I cannot fix this, this will be a show stopper
for lwIP (I hope not).

Thanks,
Tom

-- Beantwortete Nachricht --

Absender: toelke
Datum: 02.06.2014 19:07 Uhr

Hi Tom,

I would guess this comes from exhausted heap memory or exhausted TCP PCBs.

Could you check those?

Cheers,
Philipp

—
Reply to this email directly or view it on GitHub
#1 (comment).

[toelke]

Hi Tom,

yes, actually I am from Germany but I would like to keep public communication in English as others might benefit from it.

To check for heap memory, in vfs.c I should check the return value of every malloc and return some sensible value. It is possible ftpd.c relies on some return value being non-NULL.

You could try increasing heap size if that changes anything.
If you want to check how much heap is free, you would need to look into the implementation details of your runtime.
You could also single-step from cmd_list() on and check for NULL pointers being used.

How many TCP pcbs have you configured in lwip? ftp needs one listening pcb and one non-listening. If you have a webserver, it will need further pcbs.

Another thing you could look into: As in ftp the server connects back to the client, sometimes a personal firewall on the client machine can hinder a complete ftp connection.

I will probably not have time in the next four weeks to build necessary error-checking code into this module. I would gladly accept a pull request though...

I hope I can help you to get this working.

Cheers,
Philipp

[toelke]

I will close this now as I do not see how it helps to have it open; I am not sure if your problem is a error in the ftp-code or your port.