# Google SoC lwIP Report Week 7

DevFeed: [Google SoC lwIP Report Week 7](<https://devfeed.tech/articles/google-soc-lwip-report-week-7-32793.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/google-soc-lwip-report-week-7/>)

Published: 2016-07-11T00:00:00Z

Content type: article

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [lwIP](<https://devfeed.tech/topics/lwip.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [ReactOS](<https://devfeed.tech/topics/reactos.md>), [C](<https://devfeed.tech/topics/c.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Assembly](<https://devfeed.tech/topics/assembly.md>)

Tags: [assembly](<https://devfeed.tech/tags/assembly.md>), [c](<https://devfeed.tech/tags/c.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [debugger](<https://devfeed.tech/tags/debugger.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [free](<https://devfeed.tech/tags/free.md>), [google](<https://devfeed.tech/tags/google.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [lwip](<https://devfeed.tech/tags/lwip.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>)

## AI overview

A Google SoC Week 7 report describes debugging a ReactOS driver involving lwIP. The author resolved a NULL pointer dereference, received a code review identifying locking and loop problems, and began setting up WinDBG to investigate further memory access violations.

## Source excerpt

Last week ended with Art going through decompiled assembly to find a bug for me, because the stack trace in the kernel debugger was pointing me to the wrong line in the C source code. It turns out that the problem was a NULL pointer dereference in the RECEIVE callback. As always in programming, a lot of effort went into catching a small oversight. With that leftover bug from last week resolved, I moved on to my tasks for this week - more debugging, a code review done by Thomas Faber, and finally setting up WinDBG.