Method private structure allocated failure
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Start with the linked user/user_main.c example and reproduce the WPA2 Enterprise connection using ESP8266_NONOS_SDK_V2.0.0_16_08_10, recording heap usage and the “Method private structure allocated failure” output. Compare the minimal username/password case with the PEM certificate and private-key case; done means identifying the allocation failure’s cause and documenting a verified correction or limitation.
Written by the indexing model from the issue text.
Description
I added some of the enterprise functions to the basic_example and linked with wpa2, but I'm getting what sounds like an out of memory error even with this minimal program. This is with ESP8266_NONOS_SDK_V2.0.0_16_08_10, any ideas? I have the same error if I try a PEM client certificate and private key.
wifi_set_opmode(STATION_MODE);
wifi_station_set_wpa2_enterprise_auth(true);
wifi_station_set_reconnect_policy(false);
wifi_station_set_enterprise_username((u8*)EAP_USER, os_strlen(EAP_USER));
wifi_station_set_enterprise_password((u8*)EAP_PASSWORD, os_strlen(EAP_PASSWORD));
wifi_station_connect();
heap 46040 wifi status 1
state: 2 -> 0 (0)
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt
Method private structure allocated failure
Full program here.
https://github.com/dfries/source-code-examples/blob/wpa2-eap/basic_example/user/user_main.c
- Dominant language
- Makefile
- Stars
- 278
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from esp8266/source-code-examples
-
nnect Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
ji Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
ch Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in esp8266/source-code-examples
Similar issues
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
C-bug needs-triage O-AVR T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
module: unknown type: bug/reported
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenXiangShan/XiangShan#6623 ·