From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14562 invoked by alias); 25 Jun 2007 15:59:19 -0000 Received: (qmail 14524 invoked by uid 48); 25 Jun 2007 15:59:10 -0000 Date: Mon, 25 Jun 2007 15:59:00 -0000 Message-ID: <20070625155910.14523.qmail@sourceware.org> From: "swagiaal at redhat dot com" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070625134256.4698.pmuldoon@redhat.com> References: <20070625134256.4698.pmuldoon@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4698] Opening up a core file in the source window causes a backtrace 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: 2007-q2/txt/msg00418.txt.bz2 List-Id: ------- Additional Comments From swagiaal at redhat dot com 2007-06-25 15:59 ------- Are core files meant to be self containted ? If so then this is a bad core file. Why is the executable needed ? If not then there is no safe way to figure out what the executable that was used to create the is, in which case the user should specify it. So two sides to this: fcore should make sure the information is correctly retrieved, failing that frysk should be able to handle a case where the executable is unknown -- http://sourceware.org/bugzilla/show_bug.cgi?id=4698 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.