From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Andrew Cagney <ac131313@redhat.com>,
Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files
Date: Thu, 15 Jan 2004 19:13:00 -0000 [thread overview]
Message-ID: <20040115191337.GA7759@nevyn.them.org> (raw)
In-Reply-To: <4006E56E.6010803@gnu.org>
On Thu, Jan 15, 2004 at 02:09:34PM -0500, Andrew Cagney wrote:
> >Hmm, can you think of an efficient way of soaking up most of the stack
> >>...? :-) On GNU/Linux, alloca() proved to be useless :-(
> >
> >
> >The best you're likely to get is recursively calling a function with a,
> >say, 4K frame.
>
> That would unfortunatly defeat the current technique of creating a very
> large but very sparse core file. I'll see what I can cook up.
If you don't touch the stack at least once in a while, you will get
segfaults without first allocating stack space, on many platforms;
they'll look at how far down the stack you went and if you've moved
past the limit into data, they won't bother to grow the stack. I'm not
sure it's possible to get stack pages allocated that aren't backed by
allocated memory...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-15 19:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 14:56 Michael Elizabeth Chastain
2004-01-14 15:07 ` Andrew Cagney
2004-01-14 15:16 ` Daniel Jacobowitz
2004-01-14 15:38 ` Andrew Cagney
2004-01-14 15:44 ` Daniel Jacobowitz
2004-01-15 19:09 ` Andrew Cagney
2004-01-15 19:13 ` Daniel Jacobowitz [this message]
2004-01-20 22:02 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 8:18 Michael Elizabeth Chastain
2004-01-21 4:42 Michael Elizabeth Chastain
2004-01-21 5:23 ` Andrew Cagney
2004-01-14 3:11 Michael Elizabeth Chastain
2004-01-14 14:48 ` Andrew Cagney
2004-01-14 2:40 Andrew Cagney
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=20040115191337.GA7759@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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