Trying to read a not used ID server cause reset

ivanroberto commented 9 years ago

Hi Igrr,

First of all, thanks for your hard work!

I found a issue in my bench tests, that i want to share with you.

If I try to read an ID already not used, i got a reset.

I know... I can't read an ID not used, but i think that is a small bug.

Thanks a lot

AT+CIPSTA?

+CIPSTA:"10.1.68.192","255.255.255.0","10.1.68.1"
AT+CIPLISTEN="TCP",10000,2048

+CIPLISTEN:6,10000,2048

+CIPACCEPT:0,"10.1.70.126"

+CIPDR:0,6

+CIPDR:0,8
AT+CIPRD=0

+CIPRD:0,8

123456

OK

+CIPDISCONNECT:0
AT+CIPRD=0

+CIPRD:0,0

OK
AT+CIPRD=1
Fatal exception (28):
epc1=0x40247b76, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000014, depc=0x00000000

 ets Jan  8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 24112, room 16 
tail 0
chksum 0x7c
load 0x3ffe8000, len 2692, room 8 
tail 12
chksum 0xdc
ho 0 tail 12 room 4
load 0x3ffe8a90, len 8728, room 12 
tail 12
chksum 0x6a
csum 0x6a
rl

saper-2 commented 9 years ago

Hi, As I mentioned on ESP8266 forum, I have that same behavior after CIPCLOSE=conn-context-id , I have updated (added manual control connection :smile: ) my TCP-UDP-Sender app (published at github) and now I was able to pinpoint moment when the reboots happens: ESP get stuck/hung-up in moment that new connection is being created to server. And wdt_reset happens also, when I want release connection handle (context/etc) from 2nd connection (because I didn't do it just after reading data from that conn-context). So calling CIPCLOSE=0 and next CIPCLOSE=1 make ESP to wdt_reset too...

ivanroberto commented 9 years ago

Yes, I agree with you. It looks like a same issue. I hope Igrr fix it. Igrr, thanks for your precious time.

igrr / atproto

Trying to read a not used ID server cause reset #25