Cannot Insert Breakpoint 1. Error Accessing Memory Address
Contents |
| Forgot Password Login: [x] Bug14585 - "Error accessing memory address" when creating JIT internal gdb cannot insert breakpoint error accessing memory address breakpoint Summary: "Error accessing memory address" when creating JIT internal breakpoint
Error Accessing Memory Address Input/output Error
Status: RESOLVED DUPLICATE of bug 13987 Alias: None Product: gdb Classification: Unclassified Component: gdb (show other gdb cannot insert breakpoint cannot access memory at address bugs) Version: HEAD Importance: P2 normal Target Milestone: --- Assignee: Not yet assigned to anyone URL: Keywords: Depends on: Blocks: Reported: 2012-09-14 19:41 UTC by gdb break cannot access memory at address 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 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
Error In Re-setting Breakpoint 1: Cannot Access Memory At Address
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 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
Windows and many major Linux distros gdb cannot insert breakpoint 0 here . Home Help Search Login Register Wiki Code::Blocks gdb cannot access memory at address » User forums » Help » GDB having problems setting breakpoints. « previous next » Send this topic Print Pages: [1] Go Down Author Topic: GDB having problems setting breakpoints. (Read 8754 times) zalzane Single posting https://sourceware.org/bugzilla/show_bug.cgi?id=14585 newcomer Posts: 7 GDB having problems setting breakpoints. « on: June 09, 2011, 11:11:08 pm » So what I do is set a breakpoint 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\ -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug678098 - Cannot set breakpoints in gdb https://bugzilla.redhat.com/show_bug.cgi?id=678098 Summary: Cannot set breakpoints in gdb Status: CLOSED WONTFIX Aliases: None Product: Fedora http://gammon.com.au/forum/?id=3731 Classification: Fedora Component: gdb (Show other bugs) Sub Component: --- Version: 14 Hardware: x86_64 Linux Priority unspecified Severity unspecified TargetMilestone: --- TargetRelease: --- Assigned To: Jan Kratochvil QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2011-02-16 12:31 EST by Javier Jardón cannot insert Modified: 2012-08-16 09:29 EDT (History) CC List: 3 users (show) jan.kratochvil pmuldoon sergiodj See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2012-08-16 09:29:54 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment cannot insert breakpoint (proposed patch, testcase, etc.) Groups: None (edit) Description Javier Jardón 2011-02-16 12:31:42 EST I have a strange behaviour in gdb: I can't set breakpoints, this is the error: "Cannot insert breakpoint 1. Error accessing memory address 0x3b24481778: Input/output error." It's not related with SELinux, as I disabled selinux (SELINUX=permissive in /etc/selinux/config) and the problem persist. If you need any more info, please tell me. Comment 1 Jan Kratochvil 2011-02-16 12:55:57 EST (In reply to comment #0) > I have a strange behaviour in gdb: I can't set breakpoints, this is the error: > > "Cannot insert breakpoint 1. > Error accessing memory address 0x3b24481778: Input/output error." A reproducer would be the best one. Otherwise I need at least: (gdb) info breakpoints 1 and either (gdb) info proc mappings or (preferred) cat /proc/PID/maps where PID is the _debugged_ process, either from `ps axwf' or from (gdb) p getpid () Thanks. > It's not related with SELinux, as I disabled selinux (SELINUX=permissive in > /etc/selinux/config) and the problem persist. Have you rebooted afterwards? `setenforce 0' is both easier and IMO even safer method. You can verify the current status with `getenforce'. Comment 2 Fedora End Of Life 2012-08-16 09:29:57 EDT This m 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 copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-slackware-linux"... Attaching to program: /home/mud/darkwars/dwadmins/src/swr, process 562 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/libcrypt.so.1...done. Loaded symbol
Command-line: O:\CodeBlocks\MinGW\bin\gdb.exe -nx http://forums.codeblocks.org/index.php?topic=14847.0 -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 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