Cannot Insert Breakpoint Error Accessing Memory Address Input/output Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us gdb cannot insert breakpoint cannot access memory at address Learn more about Stack Overflow the company Business Learn more about hiring developers
Gdb Break Cannot Access Memory At Address
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack error in re-setting breakpoint 1: cannot access memory at address Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up After setting a breakpoint in Qt, gdb says:
Gdb Cannot Insert Breakpoint 0
“Error accessing memory address” up vote 5 down vote favorite 1 I wrote a very simple Qt program here: int main(int argc, char* argv[]) { QApplication app(argc, argv); QTableView table(&frame); table.resize(100, 100); table.show(); return app.exec(); } And when I try to set a breakpoint where the table gets clicked, I get this error from gdb: (gdb) symbol-file /usr/lib/libQtGui.so.4.4.3.debug Load new symbol table from "/usr/lib/libQtGui.so.4.4.3.debug"? (y or n) gdb cannot access memory at address y Reading symbols from /usr/lib/libQtGui.so.4.4.3.debug...done. (gdb) br 'QAbstractItemView::clicked(QModelIndex const&)' Breakpoint 1 at 0x5fc660: file .moc/release-shared/moc_qabstractitemview.cpp, line 313. (gdb) run Starting program: ./qt-test Warning: Cannot insert breakpoint 1. Error accessing memory address 0x5fc660: Input/output error. Does anyone know why the breakpoint can't be inserted? debugging qt qt4 gdb breakpoints share|improve this question edited Jul 14 '09 at 6:19 Quinn Taylor 36.6k1395118 asked May 26 '09 at 21:18 Neil 10k73448 I'm using Ubuntu Intrepid, and I have installed libqt4-dbg, if that helps at all. –Neil May 26 '09 at 21:22 add a comment| 4 Answers 4 active oldest votes up vote 2 down vote accepted If you want to automatically break in main without setting a breakpoint you can also use the start command. If you need to provide any arguments to the program you can use: start argument1 argument2 share|improve this answer edited May 29 '09 at 9:27 answered May 28 '09 at 20:57 Andy 2,4841525 add a comment| up vote 10 down vote Don't use the gdb command symbol-file to load external symbols. The breakpoint addresses will be wrong since they're not relocated. Instead, put a breakpoint in main, run the program, and then set your br
insert breakpoint -1. From: "Anmol P. Paralkar"
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 https://www.eclipse.org/forums/index.php/t/213210/ 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 Failed to execute cannot access 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 after my System.loadLibrary(mysharedlib). 2. cannot access memory 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): Status ERROR: org.eclipse.cdt.dsf.gdb code=10004 Failed to execute MI command: -exec-continue