Cannot Insert Breakpoint Input/output Error
Contents |
| Forgot Password Login: [x] Bug14585 - "Error accessing memory address" when creating JIT internal breakpoint Summary: "Error accessing memory address" when creating JIT internal breakpoint Status: RESOLVED
Cannot Insert Breakpoint Error Accessing Memory
DUPLICATE of bug 13987 Alias: None Product: gdb Classification: Unclassified Component: gdb (show gdb cannot insert breakpoint other bugs) Version: HEAD Importance: P2 normal Target Milestone: --- Assignee: Not yet assigned to anyone URL: Keywords: Depends on: gdb cannot insert breakpoint error accessing memory address Blocks: Reported: 2012-09-14 19:41 UTC by Sergio Durigan Junior Modified: 2012-09-17 18:37 UTC (History) CC List: 1 user (show) tromey See Also: Host: Target: Build: Last reconfirmed: Attachments Add an attachment (proposed
Gdb Cannot Insert Breakpoint Cannot Access Memory At Address
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 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
Gdb Break Cannot Access Memory At Address
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
[x] Bug12568 - GDB inserts breakpoint on constructor at location 0 Summary: GDB inserts breakpoint on constructor at location 0 Status: RESOLVED DUPLICATE of bug 12528 Alias: None Product: gdb Classification: Unclassified error in re-setting breakpoint 1: cannot access memory at address Component: breakpoints (show other bugs) Version: unknown Importance: P2 normal Target Milestone: --- Assignee:
Gdb Cannot Insert Breakpoint 0
Not yet assigned to anyone URL: Keywords: Depends on: Blocks: Reported: 2011-03-11 06:19 UTC by Paul Pluzhnikov Modified: 2011-03-11 08:11 UTC gdb cannot access memory at address (History) CC List: 1 user (show) dje 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 https://sourceware.org/bugzilla/show_bug.cgi?id=14585 this bug. Description Paul Pluzhnikov 2011-03-11 06:19:06 UTC When using virtual inheritance, GCC emits in-charge (C1) and not-in-charge (C2) constructors, at the same source file:line One of these ctors could be garbage-collected by the linker, causing its line table to start at location 0. GDB does not ignore that line table, sets a breakpoint on 0, then gets: Cannot insert breakpoint 1. Error accessing memory address 0x0: Input/output error. The problem reproduces with https://sourceware.org/bugzilla/show_bug.cgi?id=12568 GDB 7.2.50.20110311-cvs and GCC g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3 The problem does *not* reproduce with g++ (GCC) 4.6.0 20110219 (experimental), because in that version C1 ctor calls C2, preventing C2 from being GCd by the linker. Repro steps: /// --- foo.c struct Foo { Foo(int z) { x = z; } int x; }; struct Bar: virtual public Foo { Bar(int x) : Foo(x) { } }; int main(int argc, char *argv[]) { Foo f(42); return f.x + argc; } // Calls C2 ctor, but is GCd by linker void deadfn() { Bar b(12); } /// --- foo.c g++ -g foo.c -fno-inline -ffunction-sections -Wl,--gc-sections nm a.out | grep Foo 0000000000400622 W _ZN3FooC1Ei ### Note: only C1 constructor present! gdb ./a.out GNU gdb (GDB) 7.2.50.20110311-cvs Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later
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 https://www.eclipse.org/forums/index.php/t/213210/ Contribute Working Groups Automotive Internet of Things LocationTech Long-Term Support PolarSys Science OpenMDM Toggle navigation Home Projects Forums Eclipse Community Forums Forum Search: Search Help Register Login Home Home» Language IDEs» C / C++ IDE (CDT)» Failed to execute MI command(Eclipse and GDT/MI woes) Show: Today's Messages :: Show Polls :: Message Navigator cannot insert Failed to execute MI command [message #683459] Mon, 13 June 2011 19:47 Tom 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 cannot insert breakpoint after my System.loadLibrary(mysharedlib). 2. I then launch my "C/C++ Attach to Application" debug config, which is defined as: - 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): S