From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FMpnY-00010u-AX
	for qemu-devel@nongnu.org; Fri, 24 Mar 2006 12:10:04 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FMpnW-0000yp-LQ
	for qemu-devel@nongnu.org; Fri, 24 Mar 2006 12:10:03 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FMpnW-0000yi-BT
	for qemu-devel@nongnu.org; Fri, 24 Mar 2006 12:10:02 -0500
Received: from [65.74.133.6] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FMpoN-0000sX-JB
	for qemu-devel@nongnu.org; Fri, 24 Mar 2006 12:10:55 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Debugging low level ARM with GDB
Date: Fri, 24 Mar 2006 17:09:58 +0000
References: <4422C85F.8040106@gmail.com>
	<200603241628.34205.paul@codesourcery.com>
	<442423AF.6020400@gmail.com>
In-Reply-To: <442423AF.6020400@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200603241709.58941.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: qemu-devel@nongnu.org

On Friday 24 March 2006 16:51, Dirk Behme wrote:
> Paul Brook wrote:
> >>But PC is still wrong. Who sets the PC to KERNEL_LOAD_ADDR
> >>(0x10000)?
> >
> > What makes you think ti's wrong? There's a small bootloader built into
> > qemu.
>
> Uups. Then it seems that I start things the wrong way. I
> start QEMU with -S -s, then I attach GDB, and GDB
> "complains" that PC is at 0x0 (and not 0x10000). How do I
> have to invoke things in the correct way (and that this
> bootloader is used)  so that system is at 0x10000 if I
> attach GDB and can start with si debugging from there?

Sounds like it's working exactly as designed. You'll notice that the code at 
address zero eventually jumps to 0x10000.

Paul