public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mdaniels at lanl dot gov" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug guile/17923] scheme exception about invalid object in a backtrace
Date: Fri, 06 Feb 2015 15:28:00 -0000	[thread overview]
Message-ID: <bug-17923-4717-jmBz6OwD1f@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17923-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17923

--- Comment #2 from Marcus Daniels <mdaniels at lanl dot gov> ---
"It would be good to verify what is causing the problem.
[IOW, how is f_smob->inferior becoming NULL?]"

Unfortunately, it is only happening on a secure network with a secure code and
so it would be illegal for me to disclose any more details.  I perhaps could
find some other code with other breakpoints that acts this way.

One clarification is that the inferior is not really crashing or exiting.  It
is a periodic thing that during a run that some of the frequent breakpoints
have this property where the exception in frame-valid? occurs (obviously it
would happen in the other frame-* functions too if the precaution of modified
frame-valid? is not used).   Suppressing it in the way I said means I can't get
parent frame info, but come the next breakpoint (or the next 100), the frame-*
functions seem to work fine.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-02-06 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  6:34 [Bug guile/17923] New: " mdaniels at lanl dot gov
2015-02-06 12:24 ` [Bug guile/17923] " xdje42 at gmail dot com
2015-02-06 15:28 ` mdaniels at lanl dot gov [this message]
2015-02-07  4:26 ` mdaniels at lanl dot gov
2015-02-07  4:31 ` dje at google dot com
2015-02-07 14:46 ` dje at google dot com
2015-02-08 22:02 ` mdaniels at lanl dot gov
2015-02-11 13:57 ` xdje42 at gmail 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=bug-17923-4717-jmBz6OwD1f@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).