From: Carmelo Amoroso <carmelo73@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: CoreDump STLinux
Date: Wed, 01 Oct 2008 05:31:08 +0000 [thread overview]
Message-ID: <48E30B1C.2020502@gmail.com> (raw)
Hi Rafael,
This should be redirected to the ST support Bugzilla at
https://bugzilla.stlinux.com/
Regards,
Carmelo
rdtorres@gmail.com wrote:
> 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 :
>
> (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 ?
>
>
> Thanks in advance,
> Rafael Torres
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next reply other threads:[~2008-10-01 5:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 5:31 Carmelo Amoroso [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-30 22:26 CoreDump STLinux rdtorres
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=48E30B1C.2020502@gmail.com \
--to=carmelo73@gmail.com \
--cc=linux-sh@vger.kernel.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