similar to: [Bug 28017] New: Compiz segfaults, backtrace log and patch included

https://bugs.freedesktop.org/show_bug.cgi?id=35344 Summary: nouveau: xinit fails with message from dmesg Product: xorg Version: 7.4 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi, captured a crash on mdbox with latest mercurial: Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831

Hi, I have been going around in circles trying to find the solution. Many others appear to have the same problem, but never a solution or explanation. I am running Dovecot 2.0.21 under Fedora 16. All components are running on the same server, whose IP address is shown as '192.168.x.y'. The dovecot -n output is: <quote> /SSH Secure Shell 3.2.0 (Build 267)/ /Copyright

Hi, I started experimenting with ACLs and found I could reliably and reproducibly crash the IMAP process when trying to create a subfolder of a folder that has has ACLs set. The folder is called "Sent" with an ACL of "owner lrwstipke". I wanted to be able to have certain folders the the user cannot delete but where subfolders can be created freely. Relevant information

Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1

Found a new segfault in imap. The first log entry always happens on my mailbox, but doesn't seem to affect anything. This is CVS version from Aug. 15. dovecot: Aug 21 17:16:56 Error: 28017 IMAP(todd): Corrupted index cache file /mailhome/new/t/b/todd/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: Aug 21 17:19:44 Error: child 28017 (imap) killed with

I''m writing a method_missing handler to "automagically" create assertions from predicate functions. So, for example, one use might be: assert_not_include ''joes@shmoe.com'', response.to -or- assert_include ''info@mydomain.com'', response.from The code is working properly, but when I trigger an assert, the backtrace shows something like:

Hi all, I think it would greatly aid service debugging if we added Ruby''s backtrace information if a Service.start fails. This would be lines 1251-1255: if(NULL == hSCService){ strcpy(error,ErrorDescription(GetLastError())); CloseServiceHandle(hSCManager); rb_raise(cServiceError,error); } I''m not sure exactly how to do it, though. Or do you think it should just be

Hi, I''m using example.implementation_backtrace in a custom formatter to get the path of the file a passing spec belongs to. Following rspec on github I saw that implementation_backtrace is now deprecated and replaced by example.backtrace. Sadly it always returns nil for passed specs. So I had a look at the source and found that backtrace only gets assigned if line_number was set. Can

Hi, On some systems, I can see sometimes that Asterisk crashed before being automatically restarted (by a watch guard script). To find the root cause of this, I'm wondering if I should let asterisk run for ever with "backtrace options" DEBUG_THREADS and DONT_OPTIMIZE turned on. Which negative side effect should prevent me from doing this ? What would you suggest ? Regards

I'm using the official wine ubuntu repository and have wine1.5 and wine1.5-dbg installed. Yet when my wine application crashes, the backtrace does not have the debugging symbols. Perhaps significant is that an error message box pops up saying "internal errors - invalid parameters received". Looking at the installed files from the wine1.5-dbg package, it seems strange. It installs

I''m using ActionWebService to expose a WebService of my application, and I would like to control the error responses sent back to the client. At very least, I would like to prevent the XML to include the backtrace. How can I do this?

Hello, I current using dovecot with mdbox and on one account i get this error: doveadm(user at domain): Panic: file mail-index-sync-ext.c: line 209 (sync_ext_reorder): assertion failed: (offset < (uint16_t)-1) doveadm(user at domain): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x3fd8a) [0x7fae684fdd8a] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32)

buggzilla maintainer tell me "there's no backtrace in console output" in comment to my newly posted bug here is the bug: http://bugs.winehq.org/show_bug.cgi?id=13450 i don't understand this and if i have something to do Thank you for explanations Vincent

Morning All! Some things I noticed while playing with 3.1 master last night. 1) When using the #create! method on an association and pass "nil" vs an empty hash, now fails silently with no warning or anything. It''s almost like a no-op. I did not test to see if this behavior occurred on a basic model or not. My app''s controller was setup in such a way that I would

My app generates LLVM IR on the fly, JITs, and executes. It also has a backtrace printer installed as a signal handler, that prints a human-readable backtrace if the app crashes. Is there a succinct guide to exactly what I need to do to the LLVM IR I generate (or the calls I make to JIT) so that backtrace() and backtrace_symbols() (on Linux or OS X) can correctly print the call stack when a

Hello, I'm using wine to open a Call of duty: Modern Warfare 2 server with AlterIWNet. The server runs great with low latencies in-game, but it crashes sometimes and windows error reporting windows appears, apparently blocking the proccess from quitting, but maybe wine is blocking the quit with the backtrace that shows in console, not sure. I disabled error reporting using this:

Hello, I've just noticed that I'm getting different backtraces depending on if I use the -O2 or -O0 cflags during compilation. Here is a backtrace with -O2: http://pastebin.com/bGXCJBND And here is the one with -O0: http://pastebin.com/axPZQUaD Both were produced by the same Wine version (wine-1.3.18-170-gfa2e4bb). I'm using Fedora 14 32 bits and I always use the following CFLAGS

Hi, If you saw this topic => http://forum.winehq.org/viewtopic.php?t=12633 F.E.A.R.3 crash on startup when i launch it. This is my crash log : http://pastebin.com/38qKqEKh The problem is that i haven't got a "proper" backtrace when F.E.A.R.3.exe crash. So, i tried to get a backtrace with winedbg. Like F.E.A.R.3.exe crash very quickly, i launch these command : Code: wine

i have compiled h323 support into asterisk using channels/h323. Sometimes asterisk runs and other times it segments. I have dumped the core using asterisk -vvg and this is the back trace any pointers Core was generated by `asterisk -vvg'. Program terminated with signal 11, Segmentation fault. #0 0x400d30a6 in ?? () (gdb) bt #0 0x400d30a6 in ?? () #1 0x400305e0 in ?? () #2 0x40030714 in