search for: exc_bad_access

I'm using the latest llvm/clang 2.8 releases and am getting EXC_BAD_ACCESS crashes in ContentCache::getBuffer. This happens when I'm printing out errors from a compilation run and iterating over TextDiagnosticBuffer returned errors. When checking the errors, I construct a FullSourceLoc and do: int LineNum = SourceLoc.getInstantiationLineNumber(); int ColNum = Sourc...

...******************************************************************************** Host Name: iMac.local Date/Time: 2004-07-03 16:31:42 +0100 OS Version: 10.3.4 (Build 7H63) Report Version: 2 Command: smbd Path: /usr/sbin/smbd Version: ??? (???) PID: 653 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x002ff000 Thread 0 Crashed: 0 <<00000000>> 0xffff88a4 __memcpy + 0x104 1 smbd 0x0015ec98 talloc_memdup + 0x34 2 smbd 0x00156f5c data_blob_talloc + 0x5c 3 smbd 0x00194dd8 password_ok + 0x470 4 smbd 0x00...

...10:07:01.630 +0200 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Interval Since Last Report: 333376 sec Crashes Since Last Report: 5 Per-App Crashes Since Last Report: 1 Anonymous UUID: C67EBC9D-4A73-4DA7-B067-E5006618C178 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000074696e55 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x913d3348 _objc_search_builtins + 299 1 libobjc.A.dylib 0x91...

I switched my Common Lisp compiler to use MCJIT on the weekend and ran into a weird problem compiling one particular function. It crashes with an EXC_BAD_ACCESS error in MCJIT::finalizeObject when calling processFDE. The weird part is that the function does not appear to do anything special and I've whittled it down to the minimum size that still causes the crash. If I remove even one statement it compiles fine. Note: The function doesn't make mu...

Hello, I didn't managed to isolate the problem exactly, but I have some projects that crash (EXC_BAD_ACCESS) at launch time if I compile them using clang and integrated-as. After some svn update -r, I managed to find the culprit change. This is the commit r107943. I will try to find more info about what goes wrong. -- Jean-Daniel

...@end int main(int argc, char **argv) { return 0; } ========================================== # clang -o foo -arch i386 -framework Foundation foo.m foo.m:8:1: warning: incomplete implementation @implementation BaseNode ^ 1 warning generated. # ./foo Segmentation fault Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x6e697970 #0 0x913d3348 in _objc_search_builtins () #1 0x913d313e in __sel_registerName () #2 0x913d6269 in map_method_descs () #3 0x913d4094 in _read_images () #4 0x913e9933 in map_images_nolock () #5 0x913d30d9 in map_imag...

...Christian Schafmeister Sent: Sunday, October 13, 2013 10:52 PM To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] A weird, reproducable problem with MCJIT I switched my Common Lisp compiler to use MCJIT on the weekend and ran into a weird problem compiling one particular function. It crashes with an EXC_BAD_ACCESS error in MCJIT::finalizeObject when calling processFDE. The weird part is that the function does not appear to do anything special and I've whittled it down to the minimum size that still causes the crash. If I remove even one statement it compiles fine. Note: The function doesn't make mu...

...ul i32 %m, %x %y = add i32 %mx, %b ret i32 %y } Which looks OK to me. Note I'm not 100% sure (actually, I suspect is wrong) about the 'target datalayout' but with or without that line makes no difference to my results. When I attempt to run the JIT (interpreter works fine) I get a EXC_BAD_ACCESS with the following backtrace: * thread #1: tid = 0x2007, 0x0000000102e00042, stop reason = EXC_BAD_ACCESS (code=1, address=0x60c93a2c) frame #0: 0x0000000102e00042 frame #1: 0x00000001015c01fb LLVMPlayGround`llvm::JIT::runFunction(llvm::Function*, std::vector<llvm::GenericValue, std::all...

Hi Seems that the last round of commits makes bigdemo crash fairly quickly. Guessing it''s something to do with either the Window or fixmodule change. Program received signal EXC_BAD_ACCESS, Could not access memory. 0x00034fbc in rb_obj_is_kind_of (obj=3825080, c=1839676) at object.c:523 523 object.c: No such file or directory. Any hints? alex

...ttp://lists.llvm.org/pipermail/llvm-dev/attachments/20100709/b01cc21f/attachment.obj> -------------- next part -------------- Le 9 juil. 2010 à 15:20, Jean-Daniel Dupas a écrit : > Hello, > > I didn't managed to isolate the problem exactly, but I have some projects that crash (EXC_BAD_ACCESS) at launch time if I compile them using clang and integrated-as. > After some svn update -r, I managed to find the culprit change. This is the commit r107943. > I will try to find more info about what goes wrong. > > -- Jean-Daniel > > > > > > __________________...

llvm-generated code that runs fine on linux/i386 causes EXC_BAD_ACCESS with misaligned_stack_error_ on MacOS/i386. I read online that each function should have stack aligned by 16 on MacOS/i386 and such code should be used: Fn->addAttribute(~0U, llvm::Attribute::constructStackAlignmentFromInt(16)); But when I run clang on some C++ code I don't see alignsta...

I am creating an ExecutionEngine using the LLVMCreateExecutionEngineForModule function from the C API. I am get a set fault with the following backtrace. Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000120 0x0000000107c06643 in llvm::LLVMTargetMachine::addCommonCodeGenPasses () (gdb) bt #0 0x0000000107c06643 in llvm::LLVMTargetMachine::addCommonCodeGenPasses () #1 0x0000000107c05c6b in llvm::LLVMTargetMachine::add...

...;s still a few issues: 1) Ideally we would implement this in ControlWithItems - but that''s an abstract class, and the methods are overridden in all the subclasses (like Choice). Is there a way round this? 2) Adding this seems to cause on segfault on exit/cleanup: Program received signal EXC_BAD_ACCESS, Could not access memory. 0x00000000 in ?? () 3) It gives some compile warnings about converting void* to VALUE - I understand the problem, but I don''t know C++ correct way to cast this. Hopefully some of this can be useful elsewhere. TIA for your feedback. alex -------------- next...

This implements the wxCursor demo and includes a patch to RubyConstants.i needed to make the cursors work right. pointy.png goes into the icons directory Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

...temSettings.get_colour(xxx) segfaults for me (OS X 10.3) on a few of the constants listed in the docs. I have commented these out in the sample file for now, and the rest work as expected. For reference, running this in gdb I get the following error with the bad colours: Program received signal EXC_BAD_ACCESS, Could not access memory. 0x02da4c04 in wxColour::wxColour(wxColour const&) () 3) Wx::SystemSettings.get_font(xxx) segfaults for me for any value, so I have %ignored it for now in the .i file. For reference, gdb reports: Program received signal EXC_BAD_ACCESS, Could not access memory. 0x02d8...

...ul i32 %m, %x %y = add i32 %mx, %b ret i32 %y } Which looks OK to me. Note I'm not 100% sure (actually, I suspect is wrong) about the 'target datalayout' but with or without that line makes no difference to my results. When I attempt to run the JIT (interpreter works fine) I get a EXC_BAD_ACCESS with the following backtrace: * thread #1: tid = 0x2007, 0x0000000102e00042, stop reason = EXC_BAD_ACCESS (code=1, address=0x60c93a2c) frame #0: 0x0000000102e00042 frame #1: 0x00000001015c01fb LLVMPlayGround`llvm::JIT::runFunction(llvm::Function*, std::vector<llvm::GenericValue, std::all...

Hello, I'd like some advice on a crash that we have observed on MacOSX with the 2.8 and 2.9 releases of LLVM, but not on the top of trunk. The crash is a null-deref in llvm::JITDwarfEmitter::EmitDwarfTable : Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000 0x0000000100852203 in llvm::JITDwarfEmitter::EmitDwarfTable () at context.h:491 (gdb) bt #0 0x0000000100852203 in llvm::JITDwarfEmitter::EmitDwarfTable () at context.h:491 #1 0x0000000100859a76 in (anonymous nam...

...October 13, 2013 10:52 PM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] A weird, reproducable problem with MCJIT > > > I switched my Common Lisp compiler to use MCJIT on the weekend and ran > into a weird problem compiling one particular function. > > It crashes with an EXC_BAD_ACCESS error in MCJIT::finalizeObject when > calling processFDE. > > The weird part is that the function does not appear to do anything special > and I've whittled it down to the minimum size that still causes the crash. > If I remove even one statement it compiles fine. Note: The func...

...needs to be restarted. ********** Host Name: mailserver Date/Time: 2006-08-10 14:24:16.131 -0700 OS Version: 10.4.6 (Build 8I127) Report Version: 4 Command: dovecot Path: /opt/local/sbin/dovecot Parent: dovecot [10099] Version: ??? (???) PID: 13818 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020 Thread 0 Crashed: 0 dovecot 0x0000482c log_set_prefix + 36 (log.c:190) 1 dovecot 0x000070b0 create_mail_process + 1576 (mail-process.c:535) 2 dovecot 0x00005150 auth_master_callback + 96 (login-process.c:92) 3...

...) ) ) ============== Date/Time: 2005-07-19 11:35:30.950 +0100 OS Version: 10.4.2 (Build 8C46) Report Version: 3 Command: R Path: /Volumes/George/MyApplications/R.app/Contents/MacOS/R Parent: WindowServer [146] Version: 1.12 (1622) PID: 10493 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x68000001 Thread 0 Crashed: 0 libR.dylib 0x00303d1c Rf_isObject + 0 (util.c:623) 1 grid.so 0x060c6240 pureNullUnit + 40 (unit.c:270) 2 grid.so 0x060c6284 pureNullUnit + 108 (unit.c:273)...