[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RE : [lwip-devel] Crash Bug
From: |
Julian Gardner [RSD] |
Subject: |
RE: RE : [lwip-devel] Crash Bug |
Date: |
Fri, 18 May 2007 14:16:52 +0100 |
Also not a memory overwrite as I have my debug malloc library on and it has not
thrown up any errors.
Joolz
-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Julian Gardner [RSD]
Sent: 18 May 2007 11:42
To: lwip-devel
Subject: RE: RE : [lwip-devel] Crash Bug
Well just started debugging the assert and the address I have for struct pbuf
*p is 0x8c04260 which is NOT in my address map! Looks like something is
corrupting memory pointers.
joolz
-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Frédéric BERNON
Sent: 17 May 2007 19:20
To: lwip-devel
Subject: RE : [lwip-devel] Crash Bug
Some ideas: Simon also check in a fix for pbuf_free (in ethernetif.c, tcpip.c,
slipif.c, loopif.c). Try it...
http://savannah.nongnu.org/bugs/?19729
Another thing: do you use LWIP_SNMP? I also got a crash with last changes about
mem.c, but it seems more that snmp do a memory overwrite, and that new mem.c is
just more "sensible" to this problem (it's not sure to 100%, but I check with
Simon).
====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hidden
Web Site : http://www.hymatom.fr
====================================
P Avant d'imprimer, penser à l'environnement
-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Kieran Mansley
Envoyé : jeudi 17 mai 2007 16:36
À : lwip-devel
Objet : RE: [lwip-devel] Crash Bug
On Thu, 2007-05-17 at 15:25 +0100, Julian Gardner [RSD] wrote:
> Looking through the code it seems to use socket, setsockoption,
> select, send and recv
So the sockets API. That should have remained reasonably unchanged as far as
applications are concerned, which means it's more likely a bug in the recent
checkin.
> Is there any debug I could turn on to try and find this problem!
Perhaps the most useful thing at this stage would be to narrow it down to a
precise checkin. Can you take the CVS code from around the time that you think
it went wrong (i.e. before and after each checkin) and see which one is at
fault?
Kieran
_______________________________________________
lwip-devel mailing list
address@hidden http://lists.nongnu.org/mailman/listinfo/lwip-devel
_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel