Gdb Error Accessing Memory Address Input Output Error
Contents |
Bug8953 - breakpoint (Error accessing memory address) Summary: breakpoint (Error accessing memory address) Status: ASSIGNED Alias: None Product: gdb Classification: Unclassified Component: breakpoints (show other bugs) Version: 6.3 Importance:
Gdb Cannot Insert Breakpoint
P2 critical Target Milestone: --- Assignee: Not yet assigned to anyone URL: Keywords: gdb break cannot access memory at address Depends on: Blocks: Reported: 2005-01-20 02:28 UTC by desimoi Modified: 2008-12-18 19:42 UTC (History) CC List: 4 users (show) cannot insert breakpoint cannot access memory at address gdb-prs jacopo.desimoi kettenis mark.kettenis 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
Gdb Cannot Insert Breakpoint 0
this bug. Description desimoi 2005-01-20 02:28:00 UTC [Converted from Gnats 1848] I can't insert a breakpoint in any program, I always get an error such as: Error accessing memory address 0xblabla: Input/Output Error Release: GNU gdb 6.3 and previous Environment: Gentoo 2004.3 Linux on amd64 Kernel 2.6.9-gentoo-r9 Comment 1 mark.kettenis 2005-01-22 15:57:16 UTC From: Mark Kettenis
Error In Re-setting Breakpoint 1: Cannot Access Memory At Address
address) Date: Sat, 22 Jan 2005 16:57:16 +0100 (CET) Thanks for your bug report. Unfortunately you don't include quite enough information in the report for me to see what's wrong. My guess would be that even though you're on a 64-bit amd64 system your Linux distribution is set up such that it produces 32-bit binaries bt default. To check whether this is the case, please look at the output of: $ uname -a and $ file gdb If the first command has x86-64 somewhere in its output and the latter line says something like 32-bit ELF, my guess is probably right. In that case you can solve the problem by rebuilding gdb, making sure that you set the environment variable CC to "gcc -m64" before running configure. If my guess isn't right, please provide a self-contained testcase together with the exact commands you typed such that we can try to reproduce your problem. You can use script(1) for that. Cheers, Mark Comment 2 Mark Kettenis 2005-01-28 20:38:43 UTC From: Mark Kettenis
Windows and many major Linux distros here . Home Help Search Login Register Wiki Code::Blocks » User forums warning cannot insert breakpoint 1 » Help » GDB having problems setting breakpoints. « previous next
Gdb Cannot Access Memory At Address
» Send this topic Print Pages: [1] Go Down Author Topic: GDB having problems setting breakpoints. (Read 8814 times) zalzane Single posting newcomer Posts: 7 GDB having problems setting breakpoints. « on: June 09, 2011, 11:11:08 pm » So what I do is set a breakpoint https://sourceware.org/bugzilla/show_bug.cgi?id=8953 inside this one constructor, and go to start debug. The full debug console then spews out this info:Code: [Select]PATH=.;G:\Infinita\SDL-1.2.14\include;G:\Infinita\SDL-1.2.14\lib;O:\CodeBlocks\MinGW\bin;E:\Windows\system32;E:\Windows;E:\Windows\System32\Wbem;E:\Windows\System32\WindowsPowerShell\v1.0\
Command-line: O:\CodeBlocks\MinGW\bin\gdb.exe -nx -fullname -quiet -args bin/Debug/Infinita.exe
Working dir : G:\Infinita\
> set prompt >>>>>>cb_gdb:
Reading symbols from G:\Infinita/bin/Debug/Infinita.exe...done.
(gdb) >>>>>>cb_gdb:
> show version
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL http://forums.codeblocks.org/index.php?topic=14847.0 version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-mingw32".
For bug reporting instructions, please see:
>>>>>>cb_gdb:
> set confirm off
>>>>>>cb_gdb:
> set width 0
>>>>>>cb_gdb:
> set height 0
>>>>>>cb_gdb:
> set breakpoint pending on
>>>>>>cb_gdb:
> set print asm-demangle on
>>>>>>cb_gdb:
> set unwindonsignal on
>>>>>>cb_gdb:
> set debugevents on
>>>>>>cb_gdb:
> set new-console on
>>>>>>cb_gdb:
> set disassembly-flavor att
>>>>>>cb_gdb:
> catch throw
Catchpoint 1 (throw)
>>>>>>cb_gdb:
> source O:\CodeBlocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
>>>>>>cb_gdb:
> directory G:/Infinita/
>>>>>>cb_gdb:
> tbreak "G:/Infinita/fileIO.h:39"
warning: (Internal error: pc 0x6b in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x6b in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x6b in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x6b in read in psymtab, but not in symtab.)
Temporary breakpoint 2 at 0x
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 LocationTech Long-Term Support https://www.eclipse.org/forums/index.php/t/213210/ PolarSys Science OpenMDM Toggle navigation Home Projects Forums Eclipse Community Forums Forum Search: Search http://gammon.com.au/forum/?id=3731 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 MI command [message #683459] Mon, 13 June 2011 19:47 Tom RoweMessages: 2Registered: June 2011 Junior Member I'm cannot insert 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: - Application=Debug/libmysharedlib.so - Build config=debug - Debugger=gdb - Non-stop mode=off (although this cannot insert breakpoint 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 0x2da6: Input/output error. ' resulted in an error. !SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2011-06-13 12:06:55.727 !MESSAGE Failed to execute MI command: -exec-continue
password? Problem with breakpoints in gdb It is now over 60 days since the last post. This thread is closed.  Refresh page Posted by Greven Canada(835 posts)bio Date Thu 05 Feb 2004 10:36 PM (UTC) Message I'm trying to set a break point, but I'm getting this error: Quote:(gdb) break fight.c:525 Breakpoint 1 at 0x80e1bca: file fight.c, line 525. (gdb) cont Continuing. Warning: Cannot insert breakpoint 1. Error accessing memory address 0x80e1bca: Input/output error. The same program may be running in another process. I get similar problem when I try to boot it from within gdb,but the breakpoint is -2. My compilation flags are: Quote:DEBUG = -ggdb C_FLAGS = -g3 -g2 -W -Wall $(DEFINES) $(PROF) $(NOCRYPT) $(DBUGFLG) $(DEBUG) -export-dynamic I'm really unclear on what the problem may be, or what I can do about it. Nobody ever expects the spanish inquisition! darkwarriors.net:4848 http://darkwarriors.nettop Posted by David Haley USA(3,881 posts)bio Date Reply #1 on Fri 06 Feb 2004 01:27 AM (UTC) Message Looks like you might have the program running twice (under two separate process.) David Haley aka Ksilyan Head Programmer, Legends of the Darkstone http://david.the-haleys.orgtop Posted by Greven Canada(835 posts)bio Date Reply #2 on Fri 06 Feb 2004 01:27 AM (UTC)Amended on Fri 06 Feb 2004 01:33 AM (UTC) by Greven Message nope, only one, I checked that. This might help:dwadmins@godlike:~/src$ ps ux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND dwadmins 555 0.0 0.2 2104 1836 ? S Feb04 0:00 /bin/bash ./swr-watch dwadmins 904 0.0 0.4 6232 3204 ? S Feb04 0:00 sshd: dwadmins@pts/14 dwadmins 905 0.0 0.3 2372 2432 pts/14 S Feb04 0:00 -bash dwadmins 562 1.3 1.4 11528 11496 ? SN Feb04 21:13 swr 4848 hotboot 5 0 0 0 -1 dwadmins 2298 0.0 0.1 2788 1368 pts/14 R 18:32 0:00 ps ux dwadmins@godlike:~/src$ gdb swr 562 GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copie