Gdb Error Accessing Memory Address Bad Address
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 Learn more about Stack Overflow the
Gdb Cannot Insert Breakpoint Error Accessing Memory
company Business Learn more about hiring developers or posting ads with us Stack Overflow gdb cannot insert breakpoint cannot access memory at address Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 gdb break cannot access memory at address 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: “Error accessing memory address” up vote 5 down vote favorite 1
Gdb Cannot Insert Breakpoint 0
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) 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.
Error In Re-setting Breakpoint 1: Cannot Access Memory At Address
(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.7k1395118 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 breakpoint: gdb ./program GNU gdb 6.8-debian blah blah blah (gdb) br main Breakpoint 1 at 0x80489c1 (gdb) run Starting program: ./program Breakpoint 1, 0x080489c1 in main () (gdb) br 'QAbstractItemView::clicked(QModelIndex const&)' Breakpoint 2 at 0xb7d24664
to check the warning cannot insert breakpoint 1 nightly builds in the forum. Home Help Search
Gdb Cannot Access Memory At Address
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 http://stackoverflow.com/questions/912808/after-setting-a-breakpoint-in-qt-gdb-says-error-accessing-memory-address 8827 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 inside this one constructor, and go to start debug. The full debug console then http://forums.codeblocks.org/index.php?topic=14847.0 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
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
Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education https://community.hpe.com/t5/Languages-and-Scripting/Error-accessing-Memory/td-p/4016333 and Training Services All Services Products Integrated Systems Composable https://bugzilla.redhat.com/show_bug.cgi?id=678098 Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software gdb cannot as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software cannot insert breakpoint Defined Storage Management and Orchestration Storage Networking All Storage Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All
-Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. 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: 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: --- 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 (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 message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: