Error Accessing Memory Address 0x0 Input/output Error
Contents |
last months will be deleted periodically to fight SPAM! Home Help Search Login Register Wiki Code::Blocks » User forums » Help
Gdb Cannot Insert Breakpoint Error Accessing Memory Address
» GDB having problems setting breakpoints. « previous next » Send gdb cannot insert breakpoint cannot access memory at address this topic Print Pages: [1] Go Down Author Topic: GDB having problems setting breakpoints. (Read 8794 times) zalzane
Gdb Break Cannot Access Memory At Address
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 inside this one error in re-setting breakpoint 1: cannot access memory at address 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 version 3 or later gdb cannot insert breakpoint 0
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 0x4219ff: file G:/Infinita/fileIO.h, line 39. (2 locations)
>>>>
[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:
Gdb Cannot Access Memory At Address
None Product: gdb Classification: Unclassified Component: breakpoints (show other bugs) Version: unknown Importance: P2 normal Target Milestone: --- Assignee: 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 (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 http://forums.codeblocks.org/index.php?topic=14847.0 in before you can comment on or make changes to 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 https://sourceware.org/bugzilla/show_bug.cgi?id=12568 insert breakpoint 1. Error accessing memory address 0x0: Input/output error. The problem reproduces with 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
-Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. https://bugzilla.redhat.com/show_bug.cgi?id=678098 Bug678098 - Cannot set breakpoints in gdb Summary: Cannot set breakpoints in gdb Status: CLOSED WONTFIX Aliases: None Product: Fedora 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: gdb cannot Show dependency tree /graph Reported: 2011-02-16 12:31 EST by Javier Jardón 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: cannot access memory --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (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 (