From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10126 invoked by alias); 6 Aug 2004 17:15:28 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10119 invoked from network); 6 Aug 2004 17:15:27 -0000 Received: from unknown (HELO avtrex.com) (216.102.217.178) by sourceware.org with SMTP; 6 Aug 2004 17:15:27 -0000 Received: from avtrex.com ([192.168.0.111] RDNS failed) by avtrex.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 6 Aug 2004 10:13:36 -0700 Message-ID: <4113BC54.2050900@avtrex.com> Date: Fri, 06 Aug 2004 17:15:00 -0000 From: David Daney User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030 MIME-Version: 1.0 To: Monika Chaddha CC: gdb@sources.redhat.com Subject: Re: break instruction in mips32 References: <000001c47b9b$fc0c5330$5100a8c0@monika> In-Reply-To: <000001c47b9b$fc0c5330$5100a8c0@monika> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Aug 2004 17:13:36.0705 (UTC) FILETIME=[B5D5B310:01C47BD8] X-SW-Source: 2004-08/txt/msg00108.txt.bz2 Monika Chaddha wrote: > Hi All > > As per specification of mips32, 'break' instruction should raise the > Breakpoint Exception but gdb6.0 does not raise any break point > exception. > > As my understanding in GDB, Breakpoint implementation is done with the > help of break instruction. Whenever user puts any breakpoint the actual > instruction at that point is replaced by break instruction and the > actual instruction is maintained in other list. > > If I use break instruction in user program it does not raise any > exception. Does mips32 not support 'BREAK' instruction in GDB. > > Thanks & Regards > Monika > I am not sure what problems you are having with break, but recent official versions of binutils and linux kernel had some "issues" WRT break and the mips32 target. I don't know how these effect GDB. The problem is that "break 7" should be converted to SIGFPE, and other break codes should result in SIGTRAP. The problem I mention causes the break 7 to incorrectly SIGTRAP. This may be of no help, but I thought I would mention it anyhow. David Daney.