From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23753 invoked by alias); 19 Jun 2003 19:28:05 -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 19912 invoked from network); 19 Jun 2003 19:25:59 -0000 Received: from unknown (HELO Cantor.suse.de) (213.95.15.193) by sources.redhat.com with SMTP; 19 Jun 2003 19:25:59 -0000 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id C4CCE14F2E; Thu, 19 Jun 2003 21:25:58 +0200 (MEST) To: Zdenek Dvorak Cc: Kevin Buettner , gdb@sources.redhat.com Subject: Re: Gdb on ia64 References: <20030613110439.GA8854@atrey.karlin.mff.cuni.cz> <1030613153411.ZM2203@localhost.localdomain> <20030613180640.GC7441@atrey.karlin.mff.cuni.cz> <1030613184257.ZM6892@localhost.localdomain> <20030614123458.GA21636@atrey.karlin.mff.cuni.cz> <1030618001856.ZM676@localhost.localdomain> <20030618003601.GA30621@atrey.karlin.mff.cuni.cz> From: Andreas Schwab X-Yow: YOW!! I'm in a very clever and adorable INSANE ASYLUM!! Date: Thu, 19 Jun 2003 19:28:00 -0000 In-Reply-To: <20030618003601.GA30621@atrey.karlin.mff.cuni.cz> (Zdenek Dvorak's message of "Wed, 18 Jun 2003 02:36:01 +0200") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-SW-Source: 2003-06/txt/msg00405.txt.bz2 Zdenek Dvorak writes: |> Hello, |> |> > > > Could you tell us the address which is giving gdb problems along with |> > > > a disassembly of code near that address? (Basically, I need to see |> > > > the three instructions in the bundle.) |> > > |> > > Address: 20000000003b4c18 |> > > No function contains this address and the memory is not accessible. |> > |> > Do you know why GDB was trying to put a breakpoint there? |> |> I have no clue -- I did not ask for one and I don't know anything about gdb |> internals so I don't know why it tries to put there one on its own. Perhaps it's the shlib events breakpoint (use "maintenance info breakpoints" to list internal breakpoints). Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."