configure

OpenWRT accidental deletion of uhttpd service configuration causing LuCI management page inaccessible

01.07.2026 0, ? Software and Hardware Usage

I compiled my own OpenWRT firmware with uHTTPd providing the LuCI UI. While experimenting with server mapping I clicked delete in the top right and applied it:

After that the LuCI interface could no longer be accessed. I realized the configuration I deleted was the web server supporting LuCI. After several reboots the router functions were still normal, but the web management was gone. Dropbear SSH still worked. I was ready to reflash the firmware, but then I found this forum post:

https://forum.openwrt.org/t/cannot-access-luci-after-messing-with-settings/147903

By running the following command:

cp /rom/etc/config/uhttpd /etc/config/uhttpd

The default uhttpd configuration file is restored. Then restart the uhttpd service with service uhttpd restart, or simply reboot the router. The LuCI management page comes back without reflashing, quickly recovering access.

FFmpeg native script building Windows debug version debugging and tracing issues

24.05.2026 0, ? Design & Development

This time I want to record what feels like a rather hardcore problem. Due to the title length limit, it’s impossible to accurately express all the issues. For example, when debugging FFmpeg code with breakpoints and single‑stepping, the code does not execute in order, jumps around unpredictably, and when checking local variables near a breakpoint, their values cannot be displayed correctly, such as this:

The local variable “offset” cannot show its current value and instead displays “Variable is optimized away and not available.” From the literal meaning, we can guess that the compiler optimized the code, such as inlining and removing intermediate variables, so they can no longer be seen.

However, FFmpeg’s configure parameters for building the debug version do include:

–disable-optimizations –enable-debug –disable-stripping

These officially documented debug build parameters. So why do we still encounter all the debugging obstacles described above, which look like the result of compiler optimizations?

Continue reading…