[haiku-gsoc] Re: [ARM port] Fixing KDL memory access fault when printing the backtrace
- From: Arvind S Raj <sraj.arvind@xxxxxxxxx>
- To: haiku-gsoc <haiku-gsoc@xxxxxxxxxxxxx>
- Date: Tue, 12 Aug 2014 22:09:50 +0530
On 12 August 2014 20:03, pulkomandy <pulkomandy@xxxxxxxxxxxxx> wrote:
>
> Either way is fine. Maybe the bootloader should setup a zeroed frame in
> the kernel stack so the kernel stops there and doesn't try to analyze
> bootloader functions?
Setting up a zeroed frame sounds like a good idea. I'll work along those lines.
>>
>> Way to go to get the kdebug> prompt though, tried any KDL hangman yet? ;)
>
> "kdebug>" is the kernel debugger prompt. Besides playing kdlhangman,
> you can use it to analyze various things (interrupts, semaphores,
> threads, teams, etc.) Some help is available here:
> https://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land
>
> Is the prompt reacting to input? If not, the next step is to make that
> work. Once it does, we can try to understand why the kernel crashed and
> fix the issue, and then it will crash a little further. And we continue
> fixing issues until the userland (and bash) runs.
Yes the read_line functions and command processing are all working
fine. It's probably the case that no commands are registered (yet) as
Ithamar pointed out.
Other related posts:
