From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-44386-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 119328 invoked by alias); 28 May 2015 09:03:55 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 119317 invoked by uid 89); 28 May 2015 09:03:54 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-wg0-f46.google.com
Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 28 May 2015 09:03:53 +0000
Received: by wgez8 with SMTP id z8so30475638wge.0        for <gdb@sourceware.org>; Thu, 28 May 2015 02:03:50 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.178.227 with SMTP id db3mr3345568wjc.82.1432803830221; Thu, 28 May 2015 02:03:50 -0700 (PDT)
Received: by 10.28.142.82 with HTTP; Thu, 28 May 2015 02:03:50 -0700 (PDT)
In-Reply-To: <CAGmPkf+odifG_7f+CKAYz4EaRKwiNEawzw-afGxdLo-J1rvmXw@mail.gmail.com>
References: <CAGmPkf+odifG_7f+CKAYz4EaRKwiNEawzw-afGxdLo-J1rvmXw@mail.gmail.com>
Date: Thu, 28 May 2015 09:03:00 -0000
Message-ID: <CALeOzZ_5fUtqAMWDGro7UUvvS=wyZv5H4AAJAVpqjEQ4unuNJA@mail.gmail.com>
Subject: Re: SIGSEGV after continue
From: Shahbaz Youssefi <shabbyx@gmail.com>
To: Fei Ding <fdingiit@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2015-05/txt/msg00030.txt.bz2

Did you try looking at where SIGSEGV happens and whether it makes
sense or not? If you are accessing out of array bounds, or any other
reason for SIGSEGV, there are many reasons why it could remain
undetected.

A shortcut to debugging such cases is to run your program through `valgrind`.

On Thu, May 28, 2015 at 4:02 AM, Fei Ding <fdingiit@gmail.com> wrote:
> Hi all:
>
> I'm using gdb-7.6 and gdbserver-7.6 of android-ndk-r10d to debug
> native sharedlib (libxxx.so) on an arm android device. And I've found
> that after I set a breakpoint on some sharedlib and continue running,
> gdb tells me Program received signal SIGSEGV, Segmentation fault.
> However, if I set no bps and just run it, there will be no problem.
> What's more, I've test the same lib on another Linux, all good.
> Unfortunately, I cannot list all the differences between these two
> dev-environment, except one is Ubuntu 12 and another is Ubuntu 14.
>
> Any thoughts is helpful, thanks.