[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 4/5] Report exact PC on watchpoint hit
From: |
Paul Brook |
Subject: |
Re: [Qemu-devel] [PATCH 4/5] Report exact PC on watchpoint hit |
Date: |
Sat, 31 May 2008 16:17:03 +0100 |
User-agent: |
KMail/1.9.9 |
On Saturday 31 May 2008, Jan Kiszka wrote:
> Paul Brook wrote:
> >> @@ -2395,6 +2396,11 @@ static target_ulong check_watchpoint(tar
> >> + if (env->current_tb) {
> >> + tb_addr = env->current_tb->page_addr[0];
> >> + tb_invalidate_phys_page_range(tb_addr,
> >> + tb_addr+TARGET_PAGE_SIZE-1,
> >
> > This is wrong. env->current_tb is not what you think it it is. TB
> > chaining means we may be an any TB reachable from there.
>
> OK, I see. But the general approach to obtain the exact PC is fine? So
> should I flush the whole memory range instead?
By whole memory range you mean all of everything? That sounds a fairly poor
solution. The way arm and m68k handle this is to never put a memory op in
the middle of a TB.
Your solution also only works for targets that define TARGET_HAS_PRECISE_SMC.
Paul
- [Qemu-devel] [PATCH 0/5] Debugger enhancements, Jan Kiszka, 2008/05/31
- [Qemu-devel] [PATCH 1/5] Refactor breakpoint API and gdbstub integration, Jan Kiszka, 2008/05/31
- [Qemu-devel] [PATCH 3/5] Add read watchpoint support, Jan Kiszka, 2008/05/31
- [Qemu-devel] [PATCH 2/5] Watchpoint length and type awareness, Jan Kiszka, 2008/05/31
- [Qemu-devel] [PATCH 4/5] Report exact PC on watchpoint hit, Jan Kiszka, 2008/05/31
- [Qemu-devel] [PATCH 5/5] Enhance SMP guest debugging, Jan Kiszka, 2008/05/31
- Re: [Qemu-devel] [PATCH 0/5] Debugger enhancements, Fabrice Bellard, 2008/05/31