[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Segmentation Fault at NSThread(or NSTask)?

From: Seong-Gu Lee
Subject: Segmentation Fault at NSThread(or NSTask)?
Date: Mon, 21 Mar 2016 23:09:22 +0900

Dear gnustep developers,

I just report some malfunction.

Segmentation fault occurs as soon as executing gui application since revision 39318.
Only the message "WARNING thread xxx terminated without calling +exit!" appears when application end normally until revision 39023.

Strangely, instant re-execution(2nd round) do not make segmentation after previous segmentation fault(1st round). In addition, re-execution(3rd round) make segmentation fault after  1~2 sec(not exactly).

[testing environment ] Windows 10 x64 home, msys2/mingw32(gcc 5.3, gobjc), gnustep svn
$ ink                                 // 1st round
Segmentation fault

$ ink                                 // 2nd round (instantly)

$ ink                                 // 3rd round (after 1~2 sec)
Segmentation fault
$ gdb ./Ink.exe
(gdb) run
Starting program: D:\msys64\mingw32\GNUstep\System\Applications\Ink.app\Ink.exe
[New Thread 10172.0x204c]
[New Thread 10172.0x26fc]
[New Thread 10172.0x9f8]
[New Thread 10172.0x2624]
[New Thread 10172.0x790]

Thread 5 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 10172.0x790]
exitedThread (thread=0x0) at NSThread.m:587
587                 unregisterActiveThread((NSThread*)thread);
(gdb) bt
#0  exitedThread (thread=0x0) at NSThread.m:587
#1  0x64b44982 in ?? () from D:\msys64\mingw32\bin\libwinpthread-1.dll
#2  0x64b45597 in ?? () from D:\msys64\mingw32\bin\libwinpthread-1.dll
#3  0x67142498 in +[NSThread exit] (self=0x67253b00 <_OBJC_Class_NSThread>,
    _cmd=0x672525f0 <_OBJC_SELECTOR_TABLE+592>) at NSThread.m:837
#4  0x6713ea6f in -[NSConcreteWindowsTask _windowsTaskWatcher] (
    self=0x4d93968, _cmd=0x672526e0 <_OBJC_SELECTOR_TABLE+832>)
    at NSTask.m:1068
#5  0x671405dc in -[NSThread main] (self=0x4d95e78,
    _cmd=0x672539f8 <_OBJC_SELECTOR_TABLE+344>) at NSThread.m:1059
#6  0x67140c8d in nsthreadLauncher (thread=0x4d95e78) at NSThread.m:1166
#7  0x64b44d0d in ?? () from D:\msys64\mingw32\bin\libwinpthread-1.dll
#8  0x74e471e6 in msvcrt!_beginthreadex () from C:\Windows\SYSTEM32\msvcrt.dll
#9  0x74e472b1 in msvcrt!_endthreadex () from C:\Windows\SYSTEM32\msvcrt.dll
#10 0x751c38f4 in KERNEL32!BaseThreadInitThunk ()
   from C:\Windows\SYSTEM32\kernel32.dll
#11 0x77105de3 in ntdll!RtlUnicodeStringToInteger ()
   from C:\Windows\SYSTEM32\ntdll.dll
#12 0x04d992f8 in ?? ()
#13 0x77105dae in ntdll!RtlUnicodeStringToInteger ()
   from C:\Windows\SYSTEM32\ntdll.dll
#14 0xffffffff in ?? ()
#15 0x7712b7e6 in ntdll!RtlCaptureContext ()
   from C:\Windows\SYSTEM32\ntdll.dll
#16 0x00000000 in ?? ()
From NSTask.m:1068 of gdb log and executing timing, it may be related with pthread retain timing(would not be the exact diagnostic) at windows environment. Additionally, it worked without any error at Ubuntu 15.10 x64.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]