From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: rdtorres@gmail.com
Cc: gdb@sourceware.org
Subject: Re: CoreDump -- Cannot access memory
Date: Thu, 02 Oct 2008 06:58:00 -0000 [thread overview]
Message-ID: <200810020657.m926vShq008166@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <a7b2eccc0810011432l49ddf31tfbab10d2caa73e4f@mail.gmail.com> (rdtorres@gmail.com)
> Date: Wed, 1 Oct 2008 18:32:14 -0300
> From: rdtorres@gmail.com
>
> Do you have any idea why the stack of my core-dump is broken ?
Probably because the core dump was truncated. Usually that happens
because you're running with ulimit -c set to a value that's too small.
prev parent reply other threads:[~2008-10-02 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 21:32 rdtorres
2008-10-01 23:55 ` Paul Pluzhnikov
2008-10-02 6:58 ` Mark Kettenis [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=200810020657.m926vShq008166@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.org \
--cc=rdtorres@gmail.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