From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 387 invoked by alias); 1 Oct 2008 23:55:20 -0000 Received: (qmail 379 invoked by uid 22791); 1 Oct 2008 23:55:19 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out3.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 01 Oct 2008 23:54:21 +0000 Received: from spaceape14.eur.corp.google.com (spaceape14.eur.corp.google.com [172.28.16.148]) by smtp-out.google.com with ESMTP id m91NsFN3031355 for ; Thu, 2 Oct 2008 00:54:15 +0100 Received: from wa-out-1112.google.com (wahk34.prod.google.com [10.114.237.34]) by spaceape14.eur.corp.google.com with ESMTP id m91NqQXR021121 for ; Wed, 1 Oct 2008 16:54:13 -0700 Received: by wa-out-1112.google.com with SMTP id k34so423608wah.25 for ; Wed, 01 Oct 2008 16:54:13 -0700 (PDT) Received: by 10.115.46.10 with SMTP id y10mr10035168waj.137.1222905252950; Wed, 01 Oct 2008 16:54:12 -0700 (PDT) Received: by 10.114.78.12 with HTTP; Wed, 1 Oct 2008 16:54:12 -0700 (PDT) Message-ID: <8ac60eac0810011654r1c5093f1l798092a8f89c2460@mail.gmail.com> Date: Wed, 01 Oct 2008 23:55:00 -0000 From: "Paul Pluzhnikov" To: rdtorres@gmail.com Subject: Re: CoreDump -- Cannot access memory Cc: gdb@sourceware.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-10/txt/msg00013.txt.bz2 On Wed, Oct 1, 2008 at 2:32 PM, 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