From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24075 invoked by alias); 6 Feb 2008 18:59:39 -0000 Received: (qmail 23954 invoked by uid 48); 6 Feb 2008 18:58:56 -0000 Date: Wed, 06 Feb 2008 18:59:00 -0000 Message-ID: <20080206185856.23953.qmail@sourceware.org> From: "mark at klomp dot org" To: frysk-bugzilla@sourceware.org In-Reply-To: <20080205201316.5730.tromey@redhat.com> References: <20080205201316.5730.tromey@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/5730] stack trace does not show location information X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00296.txt.bz2 List-Id: ------- Additional Comments From mark at klomp dot org 2008-02-06 18:58 ------- (In reply to comment #3) > looks like this was broken by this commit: > bbf660ad5f803e000274503ad878040f4d604fef > > I am still running git bisect to prove it That would be somewhat surprising. Although maybe there was some side effect that explicitly set the location information from the frame. But I think you are looking in the wrong place. In comment #1 it was pointed out that the fhpd apparently knows the location information of the frame since a down and list will correctly show the source code associated with the frame. So it might make sense to look at where the fhpd list command gets this location information and make sure that the where command that shows the stack frames uses the same for printing the location string for each frame. -- What |Removed |Added ---------------------------------------------------------------------------- CC|mwielaard at redhat dot com |mark at klomp dot org http://sourceware.org/bugzilla/show_bug.cgi?id=5730 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.