Uninitialized Variables in internal.c port.h log.h about wolfssh HOT 3 CLOSED

The funny thing about this is we set -Wmaybe-uninitialized in configure. When we build the code on macOS and in Linux, using both clang and gcc, none are reporting the warning. I went through a few of these cases and the variables aren't set in error conditions and aren't referenced once the error is detected.

I'm going to get ESP-IDF up and running here. I think we have some proto boards in the office. It'll be awesome to see wolfSSH running on it.

from wolfssh.

Thanks for taking a look at this. I have a very preliminary wolfssl-esp32 repo, with the ESP32 SSH Server Project that I've been working on. (just a hobby; yes, it is a quite an ugly a hack at the moment)

I have a copy of my wolfSSH ESP IDF Component, but note it gets moved to the root directory in my local, not-yet-pushed repo changes. I have a real mess of a TCP listener at the moment with the dreaded "guru meditation panic" when a packet is received.

I have a script that will push files to the IDF, similar to the SSL Setup for Espressif, but had problems with GitHooks in Visual Studio trying to push that to GitHub. Yes, a bit odd, perhaps: I'm writing code in Visual Studio, and using WSL to compile and write firmware to the ESP32.

The plan for this weekend is to revisit this, push all the changes I have, and ask for help on the TCP Listener. I had a suggestion from Jacob today that it might be a misaligned SSL/SSH configuration. That sounds very likely as I've struggled to learn how the config works.

from wolfssh.

I think we've taken care of these items. I'm going to close this issue.

from wolfssh.