[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: signal SIGSEGV, Segmentation fault
From: |
Fred Kiefer |
Subject: |
Re: signal SIGSEGV, Segmentation fault |
Date: |
Tue, 8 May 2018 19:35:07 +0200 |
> Am 08.05.2018 um 11:27 schrieb Andreas Höschler <ahoesch@smartsoft.de>:
>
>
>> On 07 May 2018, at 23:16, Fred Kiefer <fredkiefer@gmx.de> wrote:
>
>> The best way to find out about this would be to run the application with
>> valgrind. Many mysterious problems became quite clear when looking at them
>> through the valgrind toolset. If you require help with that, I could provide
>> you with detailed instructions.
>
> I will probably need help with that. :-) How would I start?
That is a simple three steps process:
- Get and install valgrind (sudo apt-get install valgrind)
- Start your application with valgrind (valgrind Ink.app/Ink)
- Be very patient, use your application as usual and watch the messages scroll
by in the console.
And when the segmentation vault happens valgrind will be able to tell you what
caused it.
- signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/03
- Re: signal SIGSEGV, Segmentation fault, Josh Freeman, 2018/05/03
- Re: signal SIGSEGV, Segmentation fault, Riccardo Mottola, 2018/05/04
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/07
- Re: signal SIGSEGV, Segmentation fault, Fred Kiefer, 2018/05/07
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/08
- Re: signal SIGSEGV, Segmentation fault,
Fred Kiefer <=
- Re: signal SIGSEGV, Segmentation fault, Andreas Fink, 2018/05/09
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Wolfgang Lux, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Wolfgang Lux, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Riccardo Mottola, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Fred Kiefer, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Richard Frith-Macdonald, 2018/05/22