====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2008:dverkamp:journal:week6 [2008/07/02 20:34] drv |
soc:2008:dverkamp:journal:week6 [2008/07/04 09:31] (current) drv |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| * Still more debugging; no real progress yet in determining the problem with menu bzimage loading. | * Still more debugging; no real progress yet in determining the problem with menu bzimage loading. | ||
| + | |||
| + | === 03 July 2008 === | ||
| + | |||
| + | * Seems to be dying during the HTTP download, judging by DEBUG=http. Tracing deeper... | ||
| + | |||
| + | === 04 July 2008 === | ||
| + | |||
| + | * Thanks to invaluable help from Stefan, we've determined that the problem is due to the memory used for the com32 stack not being marked as used and therefore being overwritten; Stefan noted that he was working on a umalloc patch to allow multiple heaps, which could help solve this problem. Also noticed that com32 wasn't calling image_unregister like comboot; adding this, menu.c32 does work correctly on a real hardware test machine (probably by luck, noting the memory overwrites mentioned above) to boot tomsrtbt and a 16-bit COMBOOT program. However, it does not correctly boot another instance of menu.c32; more investigation to follow once the memory allocation issue is solved. | ||
