From: "Paul Pluzhnikov" <ppluzhnikov@google.com>
To: rdtorres@gmail.com
Cc: gdb@sourceware.org
Subject: Re: CoreDump -- Cannot access memory
Date: Wed, 01 Oct 2008 23:55:00 -0000 [thread overview]
Message-ID: <8ac60eac0810011654r1c5093f1l798092a8f89c2460@mail.gmail.com> (raw)
In-Reply-To: <a7b2eccc0810011432l49ddf31tfbab10d2caa73e4f@mail.gmail.com>
On Wed, Oct 1, 2008 at 2:32 PM, <rdtorres@gmail.com> wrote:
> Before running it on STLinux I'm running: ulimited -c unlimited.
> Do you have any idea why the stack of my core-dump is broken ?
The two common reasons I've seen:
- core is truncated.
- mismatch between /opt/7109/STM/STLinux-2.2/devkit/sh4/target/lib/libc.so.6
that you see on host, and what is actually used on the target.
Note that 'ulimit -c unlimited' does not guarantee that you have
a complete core: you could run into filesystem limit for example.
> Ps. Note that the memory address is a huge address ( 0x7b916ff8 ).
I am not familiar with SH, but the high value does not appear to
be unreasonable for a stack address.
Cheers,
P.S. If you have (or can build) a gdbserver for the target, you
might want to use that instead of core.
--
Paul Pluzhnikov
next prev parent reply other threads:[~2008-10-01 23:55 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 [this message]
2008-10-02 6:58 ` Mark Kettenis
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=8ac60eac0810011654r1c5093f1l798092a8f89c2460@mail.gmail.com \
--to=ppluzhnikov@google.com \
--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