Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: rdtorres@gmail.com
To: gdb@sourceware.org
Subject: CoreDump -- Cannot access memory
Date: Wed, 01 Oct 2008 21:32:00 -0000	[thread overview]
Message-ID: <a7b2eccc0810011432l49ddf31tfbab10d2caa73e4f@mail.gmail.com> (raw)

Hi all,

First of all sorry to send an email to linuxsh-dev list directly, I
doing it because my attempt to use linux-sh@m17n.org fail (its site is
down).

My problem:
I trying to analyse a core-dump of  "Hello-world" like app that is
running on SH4-STLinux, but it fails.

gdb gives me :

/opt/STM/STLinux-2.2/devkit/sh4/bin/sh4-linux-gdb mysand core
GNU gdb STMicroelectronics/Linux Base 6.4-12 [build Oct 15 2006]
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=sh4-linux"...

warning: exec file is newer than core file.
Core was generated by `./mysand'.
Program terminated with signal 6, Aborted.
Reading symbols from
/opt/7109/STM/STLinux-2.2/devkit/sh4/target/usr/lib/libstdc++.so.6...done.
Loaded symbols for
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/usr/lib/libstdc++.so.6
Reading symbols from
/opt/7109/STM/STLinux-2.2/devkit/sh4/target/lib/libm.so.6...done.
Loaded symbols for
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/lib/libm.so.6
Reading symbols from
/opt/7109/STM/STLinux-2.2/devkit/sh4/target/lib/libgcc_s.so.1...done.
Loaded symbols for
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/lib/libgcc_s.so.1
Reading symbols from
/opt/7109/STM/STLinux-2.2/devkit/sh4/target/lib/libc.so.6...done.
Loaded symbols for
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/lib/libc.so.6
Reading symbols from
/opt/7109/STM/STLinux-2.2/devkit/sh4/target/lib/ld-linux.so.2...done.
Loaded symbols for
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/lib/ld-linux.so.2
#0  0x297382d4 in raise () from
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/lib/libc.so.6
(gdb) bt full
#0  0x297382d4 in raise () from
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/lib/libc.so.6
No symbol table info available.
#1  0x29739dd6 in abort () from
/opt/7109/STM/STLinux-2.2/devkit/sh4/bin/../target/lib/libc.so.6
No symbol table info available.
Cannot access memory at address 0x7b916ff8



My program code:

#include <stdlib.h>

extern void m1();

static int count = 0;

void m3(){
       if (count++ > 2)
               abort();
       m1();
}

void m2(){
       m3();
}

void m1 (){
       m2();
}

int
main (int argc, char* argv[]) {
       m1();
       return 0;
}

I compiled it with /opt/STM/STLinux-2.2/devkit/sh4/bin/sh4-linux-g++
-g -o mysand sandbox.cpp

I've tried -fstack-protector-all option without success too.

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 ?

Ps. Note that the memory address is a huge address ( 0x7b916ff8 ).


Thanks in advance,
Rafael Torres


             reply	other threads:[~2008-10-01 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 21:32 rdtorres [this message]
2008-10-01 23:55 ` Paul Pluzhnikov
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=a7b2eccc0810011432l49ddf31tfbab10d2caa73e4f@mail.gmail.com \
    --to=rdtorres@gmail.com \
    --cc=gdb@sourceware.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