Opened 15 years ago
Closed 15 years ago
#923 closed Defect (fixed)
Fix error source for a SIGSEGV crash during exit of manager application
Reported by: | elfring | Owned by: | romw |
---|---|---|---|
Priority: | Major | Milestone: | Undetermined |
Component: | Manager | Version: | 6.6.36 |
Keywords: | SIGSEGV, invalid memory access | Cc: |
Description
I have dared to build the current development software? (release 6.9.0) on my Linux system.
I notice unexpected behaviour after I click on the X (close) button of the application window because a red "Error" was displayed in the GUI.
elfring@Sonne:~> gdb boincmgr GNU gdb (GDB; openSUSE 11.1) 6.8.50.20081120-cvs [...] (gdb) run Starting program: /usr/local/bin/boincmgr [Thread debugging using libthread_db enabled] [New Thread 0x7fffe4598950 (LWP 2732)] execvp(/home/elfring/boinc, --redirectio, --launched_by_manager) failed with error 2! execvp(/home/elfring/boinc, --redirectio, --launched_by_manager) failed with error 2! Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe4598950 (LWP 2732)] 0x00007ffff423df6a in freelocale () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff423df6a in freelocale () from /lib64/libc.so.6 #1 0x000000000043e1da in RPCThread::Entry (this=0xd8f810) at AsyncRPC.cpp:380 #2 0x00007ffff5dc9a41 in wxThreadInternal::PthreadStart(wxThread*) () from /usr/local/lib/../lib64/libwx_baseu-2.8.so.0 #3 0x00007ffff49df070 in start_thread () from /lib64/libpthread.so.0 #4 0x00007ffff42e610d in clone () from /lib64/libc.so.6 #5 0x0000000000000000 in ?? ()
Note: See
TracTickets for help on using
tickets.
This appears to be fixed in 6.10 and trunk.