From: Joel Brobecker <brobecker@gnat.com>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb@sources.redhat.com
Subject: Re: Unwinding past main
Date: Wed, 03 Nov 2004 00:14:00 -0000 [thread overview]
Message-ID: <20041103001452.GA986@gnat.com> (raw)
In-Reply-To: <20041102232929.GW4249@tausq.org>
> I'm seeing a stack unwinding problem on hppa. Seems like this should be
> applicable to other targets too -- how do you solve this problem?
Funny you would see that. I am just looking at the same sort of
problem, but on IA64. I have an infinite loop when unwinding the
call stack from a thread. I don't understand all the conditions
yet (I am completely new to IA64, and it's quite complex for me).
So you are right in saying that this can happen on other targets too.
In my case, the "main" is the NPTL thread start routine, and we try
to unwind past it. In some cases, we are lucky, because we end up
with 2 identical frames which cause an error, but in some others,
the frame base changes slightly from frame to frame and we loop...
--
Joel
next prev parent reply other threads:[~2004-11-03 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 23:29 Randolph Chung
2004-11-02 23:33 ` Randolph Chung
2004-11-03 0:14 ` Joel Brobecker [this message]
2004-11-03 0:48 ` Randolph Chung
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=20041103001452.GA986@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
--cc=randolph@tausq.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