search for: 29176

...info at dem 24303 24300 0 10:20:46 ? 0:00 rawlog /opt/csw/ libexec/dovecot/imap info at dem 29941 15780 0 10:58:09 ? 0:00 imap info at dem 28480 28477 0 - ? 0:00 <defunct> info at dem 28329 15780 0 10:46:28 ? 0:03 imap info at dem 29177 29176 0 - ? 0:00 <defunct> info at dem 28749 28748 0 - ? 0:00 <defunct> info at dem 29801 15780 0 10:56:56 ? 0:00 imap info at dem 29180 29179 0 10:52:05 ? 0:00 rawlog /opt/csw/ libexec/dovecot/imap info at dem 29635 15780 0 10:...

...| CPU states: 93.5% user, 0.0% nice, 6.1% system, 0.4% interrupt, 0.0% idle | Mem: 82M Active, 5692K Inact, 31M Wired, 4572K Cache, 8349K Buf, 616K Free | Swap: 512M Total, 402M Used, 110M Free, 79% Inuse, 5412K In, 748K Out | PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND | 29176 www -18 0 392M 85612K swread 0:57 6.83% 6.83% httpd |---cut--- Ben Laurie (team Apache) <ben@ALGROUP.CO.UK> responded swift: | And here''s a band-aid for 1.3.1 - I''m sure we''ll come up with something | better soon. This (untested) patch should prevent t...

I hope I''m not breaching etiquette too badly. It''s not my intention to offend or pressurize anyone. Also, I admit my personal motivation. I had a look at the list of pending patches (http://dev.rubyonrails.org/report/3) to get an idea what patches are currently open and see what their state is. From some of my own patches I know that they are basically ready for either

...ThreadHelper (data=<optimized out>) at util/virthreadpthread.c:161 #4 0x00007fc335097b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007fc3349daa3d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x0000000000000000 in ?? () Thread 5 (Thread 0x7fc32de79700 (LWP 29176)): #0 0x00007fc33509c2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fc3371ae9ea in virCondWait (c=c@entry=0x7fc3380dbe18, m=m@entry=0x7fc3380dbd58) at util/virthreadpthread.c:117 #2 0x00007fc3371af0eb in virThreadPoolWorker (opaque=opaque@entry=0x7f...

I am newbie to this gdb debugging. now i did the bt in the debugging. In my side still it showing the error. Following are the stacktrace which i got. Kindly refer the following logs for full information: **** [New Thread 0x7f8503695700 (LWP 20012)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007f84f671281e in

...| CPU states: 93.5% user, 0.0% nice, 6.1% system, 0.4% interrupt, 0.0% idle | Mem: 82M Active, 5692K Inact, 31M Wired, 4572K Cache, 8349K Buf, 616K Free | Swap: 512M Total, 402M Used, 110M Free, 79% Inuse, 5412K In, 748K Out | PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND | 29176 www -18 0 392M 85612K swread 0:57 6.83% 6.83% httpd |---cut--- Ben Laurie (team Apache) <ben@ALGROUP.CO.UK> responded swift: | And here's a band-aid for 1.3.1 - I'm sure we'll come up with something | better soon. This (untested) patch should prevent the worst effect...