[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] setting MIPS gdb breakpoints have wrong offsets

From: Dirk Behme
Subject: [Qemu-devel] setting MIPS gdb breakpoints have wrong offsets
Date: Sun, 11 Jun 2006 15:58:37 +0200
User-agent: Mozilla Thunderbird 1.0.7 (X11/20050923)


I just tried to debug some simple MIPS code using qemu-system-mipsel by setting some breakpoints. If I use gdb's break command with symbol names the breakpoints are set at offsets and therefore they are never hit.

Please find an example below. I'd like to stop the program if I get an interrupt, everything looks okay. But break command sets breakpoint at 0xbfc00384 instead of 0xbfc00380. Is this a bug or feature? I use qemu-system-mipsel with some of the pending MIPS patches applied locally. If this is a bug, can anybody else reproduce this? Any idea?

Best regards


(gdb) info address exception
Symbol "exception" is at 0xbfc00380.
(gdb) list exception
158     .end cache_miss
160     .org 0x380
161     .ent exception
162     exception:
163             j       exception_handler
164             nop
165     .end exception
167     /****************************************************
(gdb) x/2i 0xbfc00380
0xbfc00380 <exception>: b       0xbfc0046c <exception_handler>
0xbfc00384 <exception+4>:       nop
(gdb) break exception
Breakpoint 1 at 0xbfc00384: file crt0.S, line 163.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]