search for: threads

Hey thanks to Johann, I got wine to install correctly on my amd64. Then I installed winetools. When I run the newest build, version 2.1.1., and try to install windows software, i get this output: bash-2.05b$ winetools found gettext in /usr/bin which: no dillo in

I just bought Legend of Grimrock and I can't get it to run in wine on my Arch Linux 64 bit machine. Several users have reported getting it to work under wine in Kubuntu and on Mac with wine. When I try to run it I get the following error Code: [af at andre ~]$ env WINEPREFIX="/home/af/.local/share/wineprefixes/log" wine C:\\windows\\command\\start.exe /Unix

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 ../n...

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)

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) &q...

...1.35 on fedora core 20, for information. all the best max     Gesendet: Freitag, 26. September 2014 um 11:21 Uhr Von: "Michal Privoznik" <mprivozn@redhat.com> An: ustermann78@web.de, libvir-list@redhat.com, libvirt-users@redhat.com Betreff: Re: [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug? On 26.09.2014 09:46, ustermann78@web.de wrote: > hello, > > if i start a transient guest doamin via "virsh create abcd.xml" i see an additional libvirt thread and also some open files: > > pstree -h `pgrep libvirtd` > libv...

...etrying (60 sec) wine: Unhandled exception 0x40000015 at address 0x6f7dd5 (thread 0024), starting debugger... Process of pid=0008 has terminated No process loaded, cannot execute 'echo Modules:' Cannot get info on module while no process is loaded No process loaded, cannot execute 'echo Threads:' process tid prio (all id:s are in hex) 0000000e services.exe 00000014 0 00000010 0 0000000f 0 00000011 winedevice.exe 00000018 0 00000017 0 00000013 0 00000012 0 00000019 explorer.exe 0000001a 0 You must be attached to a process to run this command. No pr...

...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

....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's >> basically memcpy'ing input files to an output file, so the memory bandwidth >> could be a limiting factor there. But I do not see a reason to limit the >...

Hi, would be glad to be contributing with this question to all the comunity. I?m having a weird issue, suddenly I get channels on IDLE 0x00 state 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

...ution var = " << var << std::endl; // CHECK: Main execution var = 6 std::cout << "Flush status " << __xray_log_flushLog() << std::endl; // CHECK: Flush status {{.*}} __xray_unpatch(); return 0; } // Check that we're able to see two threads, each entering and exiting fA(). // TRACE-DAG: - { type: 0, func-id: [[FIDA:[0-9]+]], function: {{.*fA.*}}, cpu: {{.*}}, thread: [[THREAD1:[0-9]+]], kind: function-enter, tsc: {{[0-9]+}} } // TRACE: - { type: 0, func-id: [[FIDA]], function: {{.*fA.*}}, cpu: {{.*}}, thread: [[THREAD1]], kind:...

..., "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 impl...

...-------------------------- > > > >> 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 0...

...ain 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] System won't let me create more threads, giving up [25/Mar/2001:16:09:41] [0:Main Thread] Cleanly shutting down... [25/Mar/2001:16:09:41] [0:Main Thread] Closing all listening sockets... [25/Mar/2001:16:09:41] [0:Main Thread] Telling threads to die... [25/Mar/2001:16:09:41] [0:Main Thread] Closing sockets for admins that keep hanging aro...

...as 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 some input. The graph is reported ram usage samples 1/second. As you can see the first leaking graph goes up and doesn''t go down, the second (fixed) graph cycles properly. ** This is a Ruby issue, so if you have software using Mutex or Monito...

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_wa...

...ank 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's >> >> basically memcpy'ing input files to an output file, so the memory >> >> bandwidth >> >&...

...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 --- Thr...