On Tue, Sep 14, 2010 at 05:48:30PM +, Blue Swirl wrote:
> On Tue, Sep 14, 2010 at 5:05 PM, Edgar E. Iglesias
> wrote:
> > On Tue, Sep 14, 2010 at 04:10:27PM +, Blue Swirl wrote:
> >> On Mon, Sep 13, 2010 at 4:51 AM, Stu Grossman
> >> wrote:
> >> > I've been using qemu-12.4 to trace acces
On Tue, Sep 14, 2010 at 5:05 PM, Edgar E. Iglesias
wrote:
> On Tue, Sep 14, 2010 at 04:10:27PM +, Blue Swirl wrote:
>> On Mon, Sep 13, 2010 at 4:51 AM, Stu Grossman wrote:
>> > I've been using qemu-12.4 to trace accesses to non-existent addresses, but
>> > I've
>> > found that the PC is inco
On Tue, Sep 14, 2010 at 04:10:27PM +, Blue Swirl wrote:
> On Mon, Sep 13, 2010 at 4:51 AM, Stu Grossman wrote:
> > I've been using qemu-12.4 to trace accesses to non-existent addresses, but
> > I've
> > found that the PC is incorrect when cpu_abort() is called from within the
> > unassigned m
On Mon, Sep 13, 2010 at 4:51 AM, Stu Grossman wrote:
> I've been using qemu-12.4 to trace accesses to non-existent addresses, but
> I've
> found that the PC is incorrect when cpu_abort() is called from within the
> unassigned memory helper routines (unassigned_mem_read[bwl] and
> unassigned_mem_w
On 13.09.2010, at 06:51, Stu Grossman wrote:
> I've been using qemu-12.4 to trace accesses to non-existent addresses, but
> I've
> found that the PC is incorrect when cpu_abort() is called from within the
> unassigned memory helper routines (unassigned_mem_read[bwl] and
> unassigned_mem_write[bw
I've been using qemu-12.4 to trace accesses to non-existent addresses, but I've
found that the PC is incorrect when cpu_abort() is called from within the
unassigned memory helper routines (unassigned_mem_read[bwl] and
unassigned_mem_write[bwl]). Even nearby instructions (plus or minus 10
instructi
