I solved the GPF problem I mentioned in an earlier e-mail (see the
information below the first patch).
The patch below is needed so the single step exception bits are
cleared. It was easiest to use the predefined handler exception routine
to do the
work of executing the continue if the KGDB i
On 5/16/07, Amit S. Kale <[EMAIL PROTECTED]> wrote:
> Did you get around this problem yet?
After trying the latest version of kgdb with 2.6.17, the problem is gone.
Thanks,
Neo
>
> Can you post the output of gdb and kgdb communication for more info? To get
> the output run gdb command "set debug
> -Original Message-
> From: Amit S. Kale [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 16, 2007 4:19 AM
> To: Wessel, Jason
> Cc: kgdb-bugreport@lists.sourceforge.net; Sergei Shtylyov; Tom Rini
> Subject: Re: [PATCH] Fix singlestep exception kernel->user
> x86_64 and ia32
>
> Jaso
Did you get around this problem yet?
Can you post the output of gdb and kgdb communication for more info? To get
the output run gdb command "set debug remote 1" as soon as you start gdb.
After this gdb will print log of the communication that takes place between
the two.
-Amit
On Thursday 26
Jason,
This check
atomic_read(&cpu_doing_single_step) != -1
may result in a loss of debug events on other cpus
Changing it to
atomic_read(&cpu_doing_single_step) == raw_smp_processor_id()
corrects that problem
I see that you've checked in this change. Would you mind waiting for 24 hours
after p
