From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30933 invoked by alias); 31 Oct 2005 13:56:52 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 30904 invoked by uid 22791); 31 Oct 2005 13:56:47 -0000 Received: from shadow.prohost.de (HELO shadow.prohost.de) (216.71.84.228) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 31 Oct 2005 13:56:47 +0000 Received: from mail.lipieda (p54A752CE.dip.t-dialin.net [84.167.82.206]) by shadow.prohost.de (8.11.6/8.11.6) with ESMTP id j9VDue329773 for ; Mon, 31 Oct 2005 14:56:44 +0100 Received: from [192.168.129.50] (unknown [192.168.129.50]) by mail.lipieda (Postfix) with ESMTP id E88A0565A for ; Mon, 31 Oct 2005 14:56:39 +0100 (CET) Message-ID: <4366229E.40901@lipowsky.de> Date: Mon, 31 Oct 2005 13:56:00 -0000 From: Efim Monjak User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Re: break of time loop Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-10/txt/msg00230.txt.bz2 thanks it works with Signal interrupt. But I found an other Problem: after two steps I read from CPSR Register the ARM CPU goes into Abort Mode. I is because the GDB reads memory after a step and hier are two adressies which are not in address area of ARM CPU. Step after reading of such address cause CPU Abort Mode. What informations reads GDB. Is it possible to switch it off? Hier is a part of remote protocol 39 l = 2 + l; (gdb) info register Sending packet: $g#67...Ack Packet received: 0000000000000000F0060040040000004000000000000000000000000000000 00000000000000000F03B0040EC3D0040F03D0040D83D0040FEFFFFEA08070040000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000001F000060 r0 0x0 0 r1 0x0 0 r2 0x400006f0 1073743600 r3 0x4 4 r4 0x40 64 r5 0x0 0 r6 0x0 0 r7 0x0 0 r8 0x0 0 r9 0x0 0 r10 0x40003bf0 1073757168 r11 0x40003dec 1073757676 r12 0x40003df0 1073757680 sp 0x40003dd8 1073757656 lr 0xeafffffe -352321538 pc 0x40000708 1073743624 fps 0x0 0 cpsr 0x6000001f 1610612767 (gdb) step Sending packet: $s#73...Ack Packet received: T050B:EC3D0040;0D:D83D0040;0F:0C070040; Sending packet: $s#73...Ack Packet received: T050B:EC3D0040;0D:D83D0040;0F:10070040; Sending packet: $s#73...Ack Packet received: T050B:EC3D0040;0D:D83D0040;0F:14070040; Sending packet: $m40000714,4#5d...Ack Packet received: 0330A0E3 Sending packet: $m40003de8,4#c5...Ack Packet received: FEFFFFEA Sending packet: $meafffffe,4#f6...Ack hier seems is readed a one pointer Packet received: FFCBCC2F Sending packet: $m40003de0,4#bd...Ack Packet received: 00000000 Sending packet: $m0,4#fd...Ack hier seems to be other pointer also Packet received: 060000EA Sending packet: $me9fffffc,4#cc...Ack Packet received: FCFFFFE9 Sending packet: $m40003de4,4#c1...Ack Packet received: F03D0040 40 ch = 3; (gdb) info register Sending packet: $g#67...Ack Packet received: 0000000000000000F0060040060000004000000000000000000000000000000 00000000000000000F03B0040EC3D0040F03D0040D83D0040FEFFFFEA14070040000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000097000060 r0 0x0 0 r1 0x0 0 r2 0x400006f0 1073743600 r3 0x6 6 r4 0x40 64 r5 0x0 0 r6 0x0 0 r7 0x0 0 r8 0x0 0 r9 0x0 0 r10 0x40003bf0 1073757168 r11 0x40003dec 1073757676 r12 0x40003df0 1073757680 sp 0x40003dd8 1073757656 lr 0xeafffffe -352321538 pc 0x40000714 1073743636 fps 0x0 0 cpsr 0x60000097 1610612887 Hier CPSR shows Abort Mode (gdb) thanks