public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "swagiaal at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4698] Opening up a core file in the source window causes a backtrace
Date: Mon, 25 Jun 2007 15:59:00 -0000	[thread overview]
Message-ID: <20070625155910.14523.qmail@sourceware.org> (raw)
In-Reply-To: <20070625134256.4698.pmuldoon@redhat.com>


------- 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.


  parent reply	other threads:[~2007-06-25 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 13:43 [Bug general/4698] New: " pmuldoon at redhat dot com
2007-06-25 15:11 ` [Bug general/4698] " swagiaal at redhat dot com
2007-06-25 15:36 ` pmuldoon at redhat dot com
2007-06-25 15:59 ` swagiaal at redhat dot com [this message]
2007-06-25 16:08 ` pmuldoon at redhat dot com
2007-06-25 18:31 ` pmuldoon at redhat dot com
2007-06-25 19:33 ` npremji at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070625155910.14523.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).