Cannot Insert Breakpoint Error Accessing Memory
Contents |
| Forgot Password Login: [x] Bug14585 - "Error accessing memory address" when creating JIT internal breakpoint Summary: "Error accessing gdb cannot access memory at address breakpoint memory address" when creating JIT internal breakpoint Status: RESOLVED DUPLICATE of
Cannot Insert Breakpoint 1. Error Accessing Memory Address
bug 13987 Alias: None Product: gdb Classification: Unclassified Component: gdb (show other bugs) Version: HEAD Importance: P2
Error Accessing Memory Address Input/output Error
normal Target Milestone: --- Assignee: Not yet assigned to anyone URL: Keywords: Depends on: Blocks: Reported: 2012-09-14 19:41 UTC by Sergio Durigan Junior Modified: 2012-09-17 18:37 UTC
Gdb Cannot Insert Breakpoint Cannot Access Memory At Address
(History) CC List: 1 user (show) tromey See Also: Host: Target: Build: Last reconfirmed: Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Sergio Durigan Junior 2012-09-14 19:41:22 UTC I could not find an easy way to reproduce this bug gdb break cannot access memory at address so far. The only way I managed to do so was to: 1) git clone git://git.qemu.org/qemu.git 2) ./configure --enable-kvm --python=python2 --target-list=x86_64-softmmu --disable-uuid --disable-werror --enable-debug --enable-fdt # you will need to install the dependencies 3) gdb -q -ex 'run' /tmp/install-qemu/bin/qemu-system-x86_64 And you will see: Warning: Cannot insert breakpoint -1. Error accessing memory address 0x34e96c: Input/output error. Running git-bisect on gdb.git, I found the culprit as being: a7262466d02155f5f70422804e5971f8d5e78118 is the first bad commit commit a7262466d02155f5f70422804e5971f8d5e78118 Author: Tom Tromey
Things LocationTech Long-Term Support PolarSys Science OpenMDM More Community Marketplace Events Planet Eclipse Newsletter Videos Participate Report a Bug Forums Mailing Lists Wiki IRC How to Contribute Working Groups Automotive Internet of Things error in re-setting breakpoint 1: cannot access memory at address LocationTech Long-Term Support PolarSys Science OpenMDM Toggle navigation Home Projects Forums Eclipse gdb cannot insert breakpoint 0 Community Forums Forum Search: Search Help Register Login Home Home» Language IDEs» C / C++ IDE gdb cannot access memory at address (CDT)» Failed to execute MI command(Eclipse and GDT/MI woes) Show: Today's Messages :: Show Polls :: Message Navigator Failed to execute MI command [message #683459] Mon, 13 June 2011 19:47 Tom https://sourceware.org/bugzilla/show_bug.cgi?id=14585 RoweMessages: 2Registered: June 2011 Junior Member I'm running Helios SR2 on RHEL6 32b with CDT 7.02, GDB common 7.0, IBM J9 VM 1.5.0. I'm trying to debug a C++ module across JNI from a JUnit. 1. I launch my "JUnit" debug config and successfully breakpoint immediately after my System.loadLibrary(mysharedlib). 2. I then launch my "C/C++ Attach to Application" debug config, which is defined as: - https://www.eclipse.org/forums/index.php/t/213210/ Application=Debug/libmysharedlib.so - Build config=debug - Debugger=gdb - Non-stop mode=off (although this setting makes no difference) This Attach to Application launches, I then attach it to javaw properly, and I see 13 suspended threads. 3. I then attempt to resume C++ thread #1 (state=suspended: user request) to no avail. - Entering "info break" from the gdb console correctly shows my breakpoint in the C++ code. Further, I can successfully display code in my C++ module, so I know I have debug info present. - Entering "c" from the gdb console gives: Warning: Cannot insert breakpoint 1. Error accessing memory address 0x2da6: Input/output error. 4. When I then attempt to resume the JUnit thread, I get the expected "org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 622. occurred resuming thread." as it appears all C++ threads are still suspended. The workspace/.metadata/.log yields messages like: !ENTRY org.eclipse.cdt.dsf 4 10005 2011-06-13 12:06:55.727 !MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@68446844): Status ERROR: org.eclipse.cdt.dsf.gdb code=10004 Failed to execute MI command: -exec-continue Error message from debugger back end: Warning: Cannot insert breakpoint 1. Error accessing memory address 0x2da6: Input/output error. java.lang.Exception: Warning: Cannot insert breakpoint 1. Error accessing memory address 0x2
from GoogleSign inHidden fieldsSearch for groups or messages
FAQ Wiki Bugtracker IRC channel Developer Blog Follow us on Twitter Latest SVN Mailing List Other languages Foundation Website Useful Wiki Links Project Roadmap Getting the Source Screenshots About donations (wiki) Bookstore Computer Math and Games in Pascal Lazarus, the complete guide (only a few left) Search Advanced search « previous next » Print Pages: [1] Author Topic: How to reset gdb settings (Read 13796 times) jagorath New member Posts: 34 How to reset gdb settings « on: August 26, 2010, 02:17:50 am » I seem to have completely hosed my debugger settings within Lazarus somehow, is there a way to clear the settings so they will be restored to the default? Perhaps by deleting an .ini file?Currently I have to run without a debugger specified because if I specify one the application doesn't run. Logged Martin_fr Administrator Hero Member Posts: 4029 Re: How to reset gdb settings « Reply #1 on: August 26, 2010, 02:31:43 am » There aren't many debugger related settings, and I am not sure, if the default will be of much use (since you need to specify at least the location of gdb.exe)Lazarus settings are in the user folder/home/name/.lazarus/*C:\Users\name\AppData\Local\lazarus\*Make a backupOther setting are in your project.lpiproject.lpslps is optional, and may either be in project dir, or the above user dirC:\Users\name\AppData\Local\lazarus\projectsessions-----------Better is to just set debugger type = gdband select a gdb.exe (should be in a subfolder of your lazarus dir)in the project options, make sure you compile with debug info -g or -gwAnd make sure:- you do not strip debug info- you do not use an external debug info file Logged jagorath New member Posts: 34 Re: How to reset gdb settings « Reply #2 on: August 26, 2010, 04:51:56 am » Thanks for the reply Martin_fr, I set the debugger to C:\lazarus\mingw\bin\gdb.exe and the type GDB, and made sure -g was included in th