search for: backtraced

Hey folks, I've written a Common Lisp compiler using LLVM as the back end. I switched to MCJIT a couple of days ago. I generate DWARF debugging information for each Compile Unit, Function, LexicalBlock and line numbers (using DIBuilder). (I'm on OS X 10.8.5; XCode 5.0; ToT LLVM/Clang build rev 192521) When I check my backtraces in lldb (stock lldb from Xcode 5.0) I don't see my

MCJIT attempts to register DWARF debugging information with ELF objects, but I don't believe it does so with MachO. This is a historical artifact due to the fact that those of us who worked on the ELF part of this didn't know how to do the same thing with MachO. Notably, to get it to work correctly RuntimeDyldELF updates some headers to point to the live code before it is registered. We

I wanted to try how fast will World of Warcraft run on my new AT3N7A-I motherboard. Installed kubuntu 9.10, wine 1.1.40 from PPA, copied working World of Warcraft directory from another machine (where it works just fine under wine), removed configuration files and started wine ./Wow.exe -opengl. Unfortunately I've got the next message after Wow.exe loaded necessary files and tried to

Originally posted at http://blog.inquirylabs.com/2006/02/11/textmate- backtracer-10/ == Announcing Version 1.0 == The backtracer has been around for a while now, and seems to have done its job well enough to deserve a 1.0 mark. == What Is It? == Whenever a Rails exception occurs, it spits out a backtrace full of filenames and line numbers. I?ve often thought, ?Wouldn?t it be nice if I

I''m using RSpec on Rails and would like to clean up the backtraces, so I went looking for an RSpec equivalent to ThoughtBot''s Quiet Backtrace gem<http://thoughtbot.com/projects/quietbacktrace>. I found Spec::Runner::QuietBacktraceTweaker in the RDOCS, but I can''t figure out how to use it. Can I add something to spec_helper.rb that will utilize

Using 1.0.8, I just realized that I''ve been scrolling through pages of backtraces when rspec is supposed to clean them up for me. This is a new development machine, so I''m not sure if older versions worked or not. I''m running Ruby 1.8.6, Rails edge, Mac OS X 10.4.10. I''ve verified that the QuietBacktraceTweaker is the one that''s running.

Hello. Several months server working on asterisk 13.7 and pjproject 2.5 (installed separately). Once a day the server crashes or hangs and is familiar sores that written watchdogs. Yesterday I decided to upgrade to 13.11 and bundled pjproject (2.5.5). Solved all the problems with compilation I started asterisk several times and each time after 5-7 seconds was seg fault. So I didn't get

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:

All, I''ve found that the html view for the rspec formatter falls to pieces with Rails 2.02 and rspec 1.10. Has anyone else run into this trouble? Here''s a monkey patch that fixes the problem. A more elegant fix would be in order, but this gets the job done: Index: /Users/timcharper/www/exchange/vendor/plugins/rspec/lib/spec/runner/formatter/text_mate_formatter.rb

Hi I've got huge amounts of May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): close(/home/user/Mail/R-Help.lock) failed: Disc quota exceeded May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): Raw backtrace: 0xb0e58 -> 0xb0894 -> 0x552b4 -> 0x55508 -> 0x55774 -> 0x55d9c -> 0x5759c -> 0x57ad0 -> 0x713cc -> 0x64284 -> 0x57be0 ->

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

Seeing a problem with a certain user causing dovecot to crash when copying mail to a folder. This looks similar to a bug someone on the mailing list posted recently. Since the backtrace mentions the index, I tried deleting all of the index files for the user (including subfolders) but it had no effect. Seems that the bug still happens when creating the index for the first time.

== Announcement == http://blog.inquirylabs.com/2006/02/18/textmate-backtracer-11/ == Changes == The textmate backtracer plugin, with the insight of Jonathan Weiss, now detects whether or not the server is a Mac system. With this additional check, it''s less likely that non-Mac users will be troubled by the plugin. == What is it? == Whenever a Rails exception occurs, it spits out a

hi, I had two problems with deliver / sieve. First one is not reproducible anymore. Im using debian unstable (amd64), often dist-upgraded, with some experimental stuff too (wine i think). The first basically triggered a backtrace when confronted an email with spammassassins report headers prepended. (user_prefs: report_safe 0) However i dont have that backtrace anymore, sorry. The second

https://bugs.freedesktop.org/show_bug.cgi?id=28017 Summary: Compiz segfaults, backtrace log and patch included Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

After working with LLVM for several years now, one problem that remains unsolved is how to generate a stack backtrace for exceptions. My basic approach is simple: I have two different exception personality functions, a "lightweight" one that just does the bare minimum needed to handle exception, and a "capturing" one that (ideally) records the call frame information as it

Since upgrading to Cucumber 0.1.99.19 I''ve noticed that the backtraces appearing in the console output are of the form: Page load was not successful (Code: 500): Followed by the dump of the rails error page. That page looks fine in a browser, and it''s helpful enough to see it when save_and_open_page does its thing, but I''m pretty used to reading plain old

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

Since getting core dumps seems to be difficult sometimes, especially with login processes, I've now added code to log the backtrace when Dovecot crashes in some assert check (or some other reason why it decides to abort()). This code works with Linux and Solaris, but I don't know about BSDs. Apparently there exists libexecinfo library which could be used. I think this code could

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