From: Mark Wielaard <mark@klomp.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: libunwind Cursor.step() return values
Date: Thu, 06 Dec 2007 18:02:00 -0000 [thread overview]
Message-ID: <1196964128.3065.22.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <475821DC.3030801@redhat.com>
Hi Phil,
On Thu, 2007-12-06 at 16:22 +0000, Phil Muldoon wrote:
> I see that step == 0 means no more or unknown frames. Further down the:
>
> step = newCursor.step()
>
> returns -1 in this case. What does that mean in this case?
A mixup of error codes... It is the result of an open() call passed
around as libunwind error code, which it isn't.
I am in the middle of rewriting this code.
But -1 could be returned in theory and then would mean:
UNW_EUNSPEC, /* unspecified (general) error */
If so a new cursor couldn't be created, but that should still not lead
to the closing of fd 0 by some other code.
On irc (and a quick pair programming on vnc - that is actually pretty
cute) we tried to get the right error code across. Which seems to happen
(then -10 UNW_ENOINFO is returned), but that didn't fix bad file
descriptor closing. So I think it is unrelated, but actually some code
trying to shut down and messing up the tty.
Maybe one of the places found in the System.exit() bugzilla?
http://sourceware.org/bugzilla/show_bug.cgi?id=4299
Cheers,
Mark
prev parent reply other threads:[~2007-12-06 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 16:23 Phil Muldoon
2007-12-06 18:02 ` Mark Wielaard [this message]
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=1196964128.3065.22.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=pmuldoon@redhat.com \
/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).