[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Strange values appearing inside an LWIP packet buffer
From: |
Peter |
Subject: |
[lwip-users] Strange values appearing inside an LWIP packet buffer |
Date: |
Fri, 15 Jul 2022 07:12:18 +0100 |
Hi All,
I am seeing these curious values in the LWIP buffers,
PBUF_POOL_BUFSIZE. This is some distance after the packet data I would
normally expect to see there.
>0x20003770 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00000000 ................................
>0x20003790 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00000000 ................................
>0x200037B0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>08941800 ................................
>0x200037D0 00000000 00000000 08A01800 00000000 00000000 00000000 00000000
>00000000 .......... .....................
>0x200037F0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00000000 ................................
>0x20003810 00000000 00000000 00000000 00000000 08E81800 00000000 00000000
>08F41800 ..................è...........ô.
>0x20003830 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00000000 ................................
>0x20003850 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00000000 ................................
>0x20003870 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00000000 ................................
>0x20003890 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> ............................
Little-endian so the bytes are 08 e8 18 00 and a uint32_t would be
0x0018e808 etc.
The addresses move about which makes it hard to do a watchpoint but I
managed to catch it once and the code was some heap code, so it looked
possibly legitimate. My concern is stray pointers.
Thank you in advance for any comments.
Peter
- [lwip-users] Strange values appearing inside an LWIP packet buffer,
Peter <=