public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "spam_hole at shaw dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/15351] New: GDB should provide a way to tell if the inferior comes from a core file
Date: Tue, 09 Apr 2013 15:26:00 -0000	[thread overview]
Message-ID: <bug-15351-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15351

             Bug #: 15351
           Summary: GDB should provide a way to tell if the inferior comes
                    from a core file
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned@sourceware.org
        ReportedBy: spam_hole@shaw.ca
    Classification: Unclassified


When examining a core file, certain operations are disabled, and others may
behave differently. It would be nice to be able to query if the active inferior
is a core file. Ideally, it would be an attribute of gdb.Inferior.

(from
http://stackoverflow.com/questions/15893058/gdb-scripting-execute-command-only-if-not-debugging-core-file/)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2013-04-09 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 15:26 spam_hole at shaw dot ca [this message]
2013-04-12 18:01 ` [Bug python/15351] " tromey at redhat dot com
2023-07-06 18:20 ` tromey at sourceware dot org

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=bug-15351-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).