SIGSEGV after continue

SIGSEGV after continue

[Fei Ding]

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.

Re: SIGSEGV after continue

[Shahbaz Youssefi]

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.