[darktable-dev] All of a sudden, darktable Thread Seg faults
Hi There, Today, for some reason, darktable seg faults with the following. I used it yesterday and it worked fine. I may have updated the OS after my last use and could roll-back the update to check. Any thoughts? Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ darktable [New LWP 2506] [New LWP 2507] [New LWP 2508] [New LWP 2509] [New LWP 2510] [New LWP 2511] [New LWP 2512] [New LWP 2513] [New LWP 2514] [New LWP 2515] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0 backtrace written to /tmp/darktable_bt_XVOKYY.txt Segmentation fault (core dumped) ~ Core dump: this is darktable darktable-2.2.3-1.fc25 reporting a segfault: #0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0 #1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3790b990 in () at /lib64/libc.so.6 #3 0x in () #4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so #5 0x7f1ae45e1afe in () at /lib64/libamdocl64.so #6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so #7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so #8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so #9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so #10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so #11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so #12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so #13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so #14 0x7f1ae424140e in () at /lib64/libamdocl64.so #15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so #17 0x7f1b1c65676e in () at /lib64/libOpenCL.so #18 0x7f1b1c658647 in () at /lib64/libOpenCL.so #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0 #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so #21 0x7f1b3f9da58b in dt_opencl_init () at /usr/bin/../lib64/darktable/libdarktable.so #22 0x7f1b3f9802be in dt_init () at /usr/bin/../lib64/darktable/libdarktable.so #23 0x560f0cb71b86 in main () Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1b1d85c700 (LWP 2514)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1b1e05d700 (LWP 2513)): #0 0x7f1b379a281d in nanosleep () at /lib64/libc.so.6 #1 0x7f1b379a276a in sleep () at /lib64/libc.so.6 #2 0x7f1b3f9e228a in dt_control_worker_kicker () at /usr/bin/../lib64/darktable/libdarktable.so #3 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1b1e85e700 (LWP 2512)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1b1f05f700 (LWP 2511)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1b1705f700 (LWP 2510)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/da
Re: [darktable-dev] All of a sudden, darktable Thread Seg faults
On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis wrote: > Hi There, > > Today, for some reason, darktable seg faults with the following. I used it > yesterday and it worked fine. I may have updated the OS after my last use > and could roll-back the update to check. Any thoughts? > > Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 > x86_64 x86_64 x86_64 GNU/Linux > > $ darktable > [New LWP 2506] > [New LWP 2507] > [New LWP 2508] > [New LWP 2509] > [New LWP 2510] > [New LWP 2511] > [New LWP 2512] > [New LWP 2513] > [New LWP 2514] > [New LWP 2515] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0 > backtrace written to /tmp/darktable_bt_XVOKYY.txt > Segmentation fault (core dumped) > > ~ > > Core dump: > > this is darktable darktable-2.2.3-1.fc25 reporting a segfault: > > #0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0 > #1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at > /usr/bin/../lib64/darktable/libdarktable.so > #2 0x7f1b3790b990 in () at /lib64/libc.so.6 > #3 0x in () > #4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so So the issue *appears* to be in amd opencl blob. You can disable opencl, that would get rid of the crash. > #5 0x7f1ae45e1afe in () at /lib64/libamdocl64.so > #6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so > #7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so > #8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so > #9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so > #10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so > #11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so > #12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so > #13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so > #14 0x7f1ae424140e in () at /lib64/libamdocl64.so > #15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so > #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so > #17 0x7f1b1c65676e in () at /lib64/libOpenCL.so > #18 0x7f1b1c658647 in () at /lib64/libOpenCL.so > #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0 > #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so > #21 0x7f1b3f9da58b in dt_opencl_init () at > /usr/bin/../lib64/darktable/libdarktable.so > #22 0x7f1b3f9802be in dt_init () at > /usr/bin/../lib64/darktable/libdarktable.so > #23 0x560f0cb71b86 in main () > > Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)): > #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at > /lib64/libpthread.so.0 > #1 0x7f1b3f9e265f in dt_control_work_res () at > /usr/bin/../lib64/darktable/libdarktable.so > #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 > #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 > > Thread 10 (Thread 0x7f1b1d85c700 (LWP 2514)): > #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at > /lib64/libpthread.so.0 > #1 0x7f1b3f9e265f in dt_control_work_res () at > /usr/bin/../lib64/darktable/libdarktable.so > #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 > #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 > > Thread 9 (Thread 0x7f1b1e05d700 (LWP 2513)): > #0 0x7f1b379a281d in nanosleep () at /lib64/libc.so.6 > #1 0x7f1b379a276a in sleep () at /lib64/libc.so.6 > #2 0x7f1b3f9e228a in dt_control_worker_kicker () at > /usr/bin/../lib64/darktable/libdarktable.so > #3 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 > #4 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 > > Thread 8 (Thread 0x7f1b1e85e700 (LWP 2512)): > #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at > /lib64/libpthread.so.0 > #1 0x7f1b3f9e38be in dt_control_work () at > /usr/bin/../lib64/darktable/libdarktable.so > #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 > #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 > > Thread 7 (Thread 0x7f1b1f05f700 (LWP 2511)): > #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at > /lib64/libpthread.so.0 > #1 0x7f1b3f9e38be in dt_control_work () at > /usr/bin/../lib64/darktable/libdarktable.so > #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 > #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 > > Thread 6 (Thread 0x7f1b1705f700 (LWP 2510)): > #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at > /lib64/libpthread.so.0 > #1 0x7f1b3f9e38be in dt_control_work () at > /usr/bin/../lib64/darktable/libdarktable.so > #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 > #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 > > Thread 5 (Thread 0x7f1b1f860700 (LWP 2509)): > #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at > /lib64/libpthread.so.0 > #1 0x7f1b3f9e38be in dt_control_work () at > /usr/bin/../lib64/darktable/libdarktable.so > #2 0x7f1b3b0
Re: [darktable-dev] All of a sudden, darktable Thread Seg faults
Yes, I found that clinfo seg faults as well. So not sure if it's with the AMD libs, the open source driver piece or a kernel update that's making this happen. On 2017-04-05 12:42, Roman Lebedev wrote: On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis wrote: Hi There, Today, for some reason, darktable seg faults with the following. I used it yesterday and it worked fine. I may have updated the OS after my last use and could roll-back the update to check. Any thoughts? Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ darktable [New LWP 2506] [New LWP 2507] [New LWP 2508] [New LWP 2509] [New LWP 2510] [New LWP 2511] [New LWP 2512] [New LWP 2513] [New LWP 2514] [New LWP 2515] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0 backtrace written to /tmp/darktable_bt_XVOKYY.txt Segmentation fault (core dumped) ~ Core dump: this is darktable darktable-2.2.3-1.fc25 reporting a segfault: #0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0 #1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3790b990 in () at /lib64/libc.so.6 #3 0x in () #4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so So the issue *appears* to be in amd opencl blob. You can disable opencl, that would get rid of the crash. #5 0x7f1ae45e1afe in () at /lib64/libamdocl64.so #6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so #7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so #8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so #9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so #10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so #11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so #12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so #13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so #14 0x7f1ae424140e in () at /lib64/libamdocl64.so #15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so #17 0x7f1b1c65676e in () at /lib64/libOpenCL.so #18 0x7f1b1c658647 in () at /lib64/libOpenCL.so #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0 #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so #21 0x7f1b3f9da58b in dt_opencl_init () at /usr/bin/../lib64/darktable/libdarktable.so #22 0x7f1b3f9802be in dt_init () at /usr/bin/../lib64/darktable/libdarktable.so #23 0x560f0cb71b86 in main () Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1b1d85c700 (LWP 2514)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1b1e05d700 (LWP 2513)): #0 0x7f1b379a281d in nanosleep () at /lib64/libc.so.6 #1 0x7f1b379a276a in sleep () at /lib64/libc.so.6 #2 0x7f1b3f9e228a in dt_control_worker_kicker () at /usr/bin/../lib64/darktable/libdarktable.so #3 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1b1e85e700 (LWP 2512)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1b1f05f700 (LWP 2511)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1b1705f700 (LWP 2510)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1b1f860700 (LWP 2509)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
Re: [darktable-dev] All of a sudden, darktable Thread Seg faults
Yep, darktable opens fine with opencl disabled, so clearly an (amd driver/lib?) opencl issue. On 2017-04-05 13:01, Mark Heieis wrote: Yes, I found that clinfo seg faults as well. So not sure if it's with the AMD libs, the open source driver piece or a kernel update that's making this happen. On 2017-04-05 12:42, Roman Lebedev wrote: On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis wrote: Hi There, Today, for some reason, darktable seg faults with the following. I used it yesterday and it worked fine. I may have updated the OS after my last use and could roll-back the update to check. Any thoughts? Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ darktable [New LWP 2506] [New LWP 2507] [New LWP 2508] [New LWP 2509] [New LWP 2510] [New LWP 2511] [New LWP 2512] [New LWP 2513] [New LWP 2514] [New LWP 2515] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0 backtrace written to /tmp/darktable_bt_XVOKYY.txt Segmentation fault (core dumped) ~ Core dump: this is darktable darktable-2.2.3-1.fc25 reporting a segfault: #0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0 #1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3790b990 in () at /lib64/libc.so.6 #3 0x in () #4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so So the issue *appears* to be in amd opencl blob. You can disable opencl, that would get rid of the crash. #5 0x7f1ae45e1afe in () at /lib64/libamdocl64.so #6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so #7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so #8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so #9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so #10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so #11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so #12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so #13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so #14 0x7f1ae424140e in () at /lib64/libamdocl64.so #15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so #17 0x7f1b1c65676e in () at /lib64/libOpenCL.so #18 0x7f1b1c658647 in () at /lib64/libOpenCL.so #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0 #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so #21 0x7f1b3f9da58b in dt_opencl_init () at /usr/bin/../lib64/darktable/libdarktable.so #22 0x7f1b3f9802be in dt_init () at /usr/bin/../lib64/darktable/libdarktable.so #23 0x560f0cb71b86 in main () Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1b1d85c700 (LWP 2514)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1b1e05d700 (LWP 2513)): #0 0x7f1b379a281d in nanosleep () at /lib64/libc.so.6 #1 0x7f1b379a276a in sleep () at /lib64/libc.so.6 #2 0x7f1b3f9e228a in dt_control_worker_kicker () at /usr/bin/../lib64/darktable/libdarktable.so #3 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1b1e85e700 (LWP 2512)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1b1f05f700 (LWP 2511)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1b1705f700 (LWP 2510)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start
Re: [darktable-dev] All of a sudden, darktable Thread Seg faults
Il 05/04/2017 22:36, Mark Heieis ha scritto: > > Yep, darktable opens fine with opencl disabled, so clearly an (amd > driver/lib?) opencl issue. > Then you should fill a bugreport on AMD support website, so that they can fix it ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
