Gdb Error Accessing Memory Address I O Error
Contents |
Bug8953 - breakpoint (Error accessing memory address) Summary: breakpoint (Error accessing memory address) Status: ASSIGNED Alias: None Product: gdb Classification: gdb cannot insert breakpoint 0 Unclassified Component: breakpoints (show other bugs) Version: 6.3 Importance: P2 critical Target
Warning Cannot Insert Breakpoint 1
Milestone: --- Assignee: Not yet assigned to anyone URL: Keywords: Depends on: Blocks: Reported: 2005-01-20 02:28 UTC gdb cannot access memory at address by desimoi Modified: 2008-12-18 19:42 UTC (History) CC List: 4 users (show) 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 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
"here I am" post here to differ human beings from SPAM bots. Home Help Search Login Register Wiki Code::Blocks » 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 8815 times) zalzane Single posting newcomer https://sourceware.org/bugzilla/show_bug.cgi?id=8953 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\
Command-line: O:\CodeBlocks\MinGW\bin\gdb.exe -nx -fullname -quiet -args http://forums.codeblocks.org/index.php?topic=14847.0 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
Catchpoint 1 (throw)
>>>>>>cb_gdb:
> source O:\CodeBlocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
>>>>>>cb_gdb:
> direct
编辑kernel source目录下生成的.config文件, 禁用CONFIG_DEBUG_RODATA=n (read only data)重新编译即可 http://www.mail-archive.com/kgdb-bugreport@lists.sourceforge.net/msg03464.html Hi Folks, I’m wondering if anyone has http://abcdxyzk.github.io/blog/2014/02/28/debug-kgdb-breakpoint/ had issues with setting breakpoints. I’m able to break into the kernel, access data, do a backtrace, etc, but https://www.objc.io/issues/19-debugging/lldb-debugging/ when I attempt to set a breakpoint, then continue, I get the following error: Cannot insert breakpoint 1. gdb cannot Error accessing memory address 0xffffffff81310931: Unknown error 4294967295. I’m attaching a sample session, I had set remote debug to 1 Thanks! Pat Thomson Hi Thomson, It seems that your problem is the CONFIG_DEBUG_RODATA option was enabled, It is cannot insert breakpoint recommend to turn CONFIG_DEBUG_RODATA off when using kgdb. From the kgdb document(DocBook/kgdb.tmpl): If the architecture that you are using supports the kernel option CONFIG_DEBUG_RODATA, you should consider turning it off. This option will prevent the use of software breakpoints because it marks certain regions of the kernel's memory space as read-only. If kgdb supports it for the architecture you are using, you can use hardware breakpoints if you desire to run with the CONFIG_DEBUG_RODATA option turned on, else you need to turn off this option. Thanks, Dongdong Posted by kk 2014-02-28 17:55:00 debug, kgdb « Connecting Two Virtual Machines KGDB配置 » Copyright © 2016 - kk - Powered by Octopress