search for: thread

...r/.wine/drive_c Wine 20050111 wine is executed as wine Parameters are --noexit Version of Wine is OK. Calls to wine are executed as wine. Config is /home/webster/.wine/winetools.log. CDROM is /mnt/cdrom. Choice is Install Windows system software \*new\* fake Windows drive wine: Unhandled exception (thread 0009), starting debugger... wine: Unhandled exception (thread 000b), starting debugger... wine: Unhandled exception (thread 000d), starting debugger... wine: Unhandled exception (thread 000f), starting debugger... wine: Unhandled exception (thread 0011), starting debugger... wine: Unhandled excepti...

.../af/.local/share/wineprefixes/log/dosdevices/c:/users/Public/Desktop/Legend\ of\ Grimrock.lnk fixme:exec:SHELL_execute flags ignored: 0x00000100 fixme:exec:SHELL_execute flags ignored: 0x00004100 [af at andre ~]$ fixme:heap:HeapSetInformation (nil) 1 (nil) 0 err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threa...

Hello, sorry for my later answer. so, after i started libvirtd (no vm´s running) and attach gdb i get the following threads (gdb) info thread Id Target Id Frame 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 10 Thread 0x7f18fe74d700 (LWP 20696) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../...

I am getting all these messages when run `passenger-status''. Do I need to worry about this? I am using passenger 2.2.2 with puppet 0.24.8 and apache2 on ubuntu 9.04. I installed it using the wiki http://reductivelabs.com/trac/puppet/wiki/UsingPassenger Thread ''Main thread'': in ''int Server::start()'' (ApplicationPoolServerExecutable.cpp:553) Thread ''Status report thread'': in ''void Passenger::ApplicationPoolStatusReporter::threadMain()'' (ApplicationPoolStatusReporter.h:100)...

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

...tum: Wed, 01 Oct 2014 18:12:45 +0200 ------------------------------------------------- > On 01.10.2014 10:31, web2 wrote: >> Hello, >> >> sorry for my later answer. >> >> so, after i started libvirtd (no vm´s running) and attach gdb i get the >> following threads >> >> (gdb) info thread >> Id Target Id Frame >> 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" >> pthread_cond_wait@@GLIBC_2.3.2 () at >> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 >> 10 Thread 0x7f18fe74d700 (LWP 20696) &...

Hi Michal, thank you for your answer. so if i understand that correctly, no matter if i shutdown or destroy the domain and no matter if it is a transient or an persistent vm, the thread should disappear, right? in my case they still exist, also an hour after i destroy the domain (and don´t start any new one). i use libvirt-1.1.35 on fedora core 20, for information. all the best max     Gesendet: Freitag, 26. September 2014 um 11:21 Uhr Von: "Michal Privoznik" <mpr...

...or context 0x1 err:ole:CoGetClassObject class {0968e258-16c7-4dba-aa86-462dd61e31a3} not registered err:ole:CoGetClassObject no class object {0968e258-16c7-4dba-aa86-462dd61e31a3} could be created for context 0x1 err:ntdll:RtlpWaitForCriticalSection section 0x151b25c "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x151b25c "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x151b25c "?" wait timed out in thread 0009, blocked by 0024, retryi...

...this problem reported by Frank Hoonhout. Asterisk runs fine for a few minutes and then stops accepting new calls. (I have a standalone server with SIP phones and I'm not doing any external registration). Asterisk CVS-04/07/03-09:28:50 0x420e0037 in poll () from /lib/i686/libc.so.6 (gdb) info threads 16 Thread 14351 (LWP 7258) 0x420e187e in select () from /lib/i686/libc.so.6 15 Thread 16398 (LWP 7371) 0x420292e5 in sigsuspend () from /lib/i686/libc.so.6 14 Thread 12301 (LWP 7256) 0x420e0037 in poll () from /lib/i686/libc.so.6 13 Thread 11276 (LWP 7255) 0x420b4b31 in nanosleep ()...

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org

On Thu, Nov 17, 2016 at 1:20 PM, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Thank you for the explanation! That makes sense. >> >> Unlike ThinLTO, each thread in LLD consumes very small amount of memory >> (probably just a few megabytes), so that's not a problem for me. At the >> final stage of linking, we spawn threads to copy section contents and apply >> relocations, and I guess that causes a lot of memory traffic because that...

...tate until I do a dahdi restart. Trying to do a call trace to see whats going on deeper, I get surprised when tried to open the .call file to see the log this is incomplete. This is what I see [root at localhost telefonica]# nano chan-9-backward-804-20130507123100.call ..... [12:31:01:846] [Thread: 3067460464] [Chan 9] - Getting ANI digit 3 [12:31:01:846] [Thread: 3067460464] [Chan 9] - ANI so far: 1152723, expected length: 10 [12:31:01:846] [Thread: 3067460464] [Chan 9] - MF Tx >> 5 [ON] [12:31:01:846] [Thread: 3067460464] [Chan 9] - scheduled timer id 13 (mf_back_cycle) [12:31:01:906...

Hello, I am initializing FDR mode and finalizing/flushing the buffers manually. XRay does not log calls from the main thread unless there is a function call after __xray_log_finalize(). This behavior is abnormal since one would expect the trace file to contain all function calls made up to the point when __xray_log_finalize() is called. To demonstrate this behavior, I have taken the test case from TestCases/Posix and mod...

..., "failed: error is %s\n", guestfs_last_error (g)); > } > > and: > > guestfs_push_error_handler (g, NULL, NULL); > guestfs_some_call (g); > guestfs_pop_error_handler (g); > > Neither of these would be safe if we allowed the handle to be used > from threads concurrently, since the error string or error handler > could be changed by another thread. > > Solve this in approximately the same way that libvirt does: by making > the error, current error handler, and stack of error handlers use > thread-local storage (TLS). > > The imp...

...-------------------------- > > > >> On 01.10.2014 10:31, web2 wrote: >> >>> Hello, >>> >>> sorry for my later answer. >>> >>> so, after i started libvirtd (no vm´s running) and attach gdb i get the >>> following threads >>> >>> (gdb) info thread >>> Id Target Id Frame >>> 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" >>> pthread_cond_wait@@GLIBC_2.3.2 () at >>> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 >>> 10 Thread...

I'm having problems with this combination. I thought it was problems with Ices but I'm not so sure... I start Icecast and Ices and send them to the background. Usually about 10-12 hours later, they are dead. The icecast.log file shows this: [25/Mar/2001:16:09:41] [0:Main Thread] ERROR: Could not create new thread, retrying [25/Mar/2001:16:09:41] [0:Main Thread] ERROR: Could not create new thread, retrying [25/Mar/2001:16:09:41] [0:Main Thread] ERROR: Could not create new thread, retrying [25/Mar/2001:16:09:41] [0:Main Thread] ERROR: Could not create new thread, retrying [...

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for whatever reason) is to use Sync and put it in a block: http://pastie.caboo.se/10317 Those two scripts are mini versions of how Mongrel manages threads so that I could figure out a solution or get...

On 01.10.2014 10:31, web2 wrote: > Hello, > > sorry for my later answer. > > so, after i started libvirtd (no vm´s running) and attach gdb i get the following threads > > (gdb) info thread > Id Target Id Frame > 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 > 10 Thread 0x7f18fe74d700 (LWP 20696) "libvirtd" pthread_cond_w...

...at freebsd.org> wrote: >> >> On Thu, Nov 17, 2016 at 1:20 PM, Rafael Espíndola via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> >> >> >> Thank you for the explanation! That makes sense. >> >> >> >> Unlike ThinLTO, each thread in LLD consumes very small amount of memory >> >> (probably just a few megabytes), so that's not a problem for me. At the >> >> final stage of linking, we spawn threads to copy section contents and >> >> apply >> >> relocations, and I guess that c...

...EBP=0196F958 ESP=0196F940 EIP=37416993 FLG=00010202 CS =0073 DS =007B ES =007B SS =007B FS =0033 GS =003B ---------------------------------------- Stack Trace (Manual) ---------------------------------------- Address Frame Logical addr Module Showing 19/19 threads... --- Thread ID: 55 --- **** Unable to retrieve thread context, error: 5 --- Thread ID: 56 --- **** Unable to retrieve thread context, error: 5 --- Thread ID: 57 --- **** Unable to retrieve thread context, error: 5 --- Thread ID: 58 --- **** Unable to retrieve thread context, error: 5 --- Th...