Re: kgdb on arm for 2.6

> Sorry about that.  I meant to include the rest but somehow forgot.   The 
> 'default' section calls kgdb_arch_handle_exception() which doesn't 
> appear to handle the 's' command as shown below:
>
> int kgdb_arch_handle_exception(int exception_vector, int signo,
>                   int err_code, char *remcom_in_buffer,
>                   char *remcom_out_buffer,
>                   struct pt_regs *linux_regs)
> {
>    long addr;
>    char *ptr;
>
>    switch (remcom_in_buffer[0]) {
>    case 'c':
>        kgdb_contthread = NULL;
>
>        /*
>         * Try to read optional parameter, pc unchanged if no parm.
>         * If this was a compiled breakpoint, we need to move
>         * to the next instruction or we will just breakpoint
>         * over and over again.
>         */
>        ptr = &remcom_in_buffer[1];
>        if (kgdb_hex2long(&ptr, &addr)) {
>            linux_regs->ARM_pc = addr;
>        } else if (compiled_break == 1) {
>            linux_regs->ARM_pc += 4;
>        }
>        compiled_break = 0;
>
>        return 0;
>    }
>
>    return -1;
> }
Hmm...  Well that just won't do.  I suppose it is possible that ARM does not 
have the single step hardware, but in this case, I assume the kgdb stub has 
to do a lot more.
--
George Anzinger   george@xxxxxxxxxx
HRT (High-res-timers):  http://sourceforge.net/projects/high-res-timers/


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click