From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>,
gdb-patches@sourceware.org,
Ian Lance Taylor <iant@google.com>
Subject: Re: [patch] Support -fsplit-stack (previous frame inner to this frame)
Date: Tue, 23 Nov 2010 20:41:00 -0000 [thread overview]
Message-ID: <m3k4k33h9q.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20101123021159.GA19258@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue, 23 Nov 2010 03:11:59 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> + /* Start and end of the `__morestack' function. MORESTACK_END address is
Jan> + the end plus one (exclusive) one. */
One of the "one"s seems redundant.
Jan> + CORE_ADDR morestack_start, morestack_end;
Is it impossible for __morestack to appear in multiple objfiles? What
if you have a program that dlmopen()s two versions of the shared library
defining it? I don't know how strict we want to be about this kind of
thing -- we don't actually support dlmopen in any meaningful way right
now anyway.
I think this would also need to hook into objfile_relocate.
A new frame type seems like an ok idea.
I don't mind this approach, though I'm also interested to hear what
others think.
Tom
next prev parent reply other threads:[~2010-11-23 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 0:13 Jan Kratochvil
2010-11-23 0:34 ` Doug Evans
2010-11-23 2:12 ` Jan Kratochvil
2010-11-23 20:41 ` Tom Tromey [this message]
2010-11-23 22:38 ` Ian Lance Taylor
2010-11-24 0:29 ` Jan Kratochvil
2010-11-24 18:34 ` Tom Tromey
2011-01-03 13:11 ` Jan Kratochvil
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=m3k4k33h9q.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=iant@google.com \
--cc=jan.kratochvil@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