Error Accessing Memory Address 0x6 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 gdb cannot insert breakpoint error accessing memory bugs) Version: 6.3 Importance: P2 critical Target Milestone: --- Assignee: Not yet assigned gdb break cannot access memory at address to anyone URL: Keywords: Depends on: Blocks: Reported: 2005-01-20 02:28 UTC by desimoi Modified: 2008-12-18 19:42 UTC (History) cannot insert breakpoint cannot access memory at address 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 error in re-setting breakpoint 1: cannot access memory at address 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
Gdb Cannot Insert Breakpoint 0
To: desimoi@sns.it Cc: gdb-gnats@sources.redhat.com Subject: Re: breakpoints/1848: breakpoint (Error accessing memory 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
Visited Search Results View More Blog Recent Blog Posts View More PMs Unread PMs Inbox Send New PM View More Page Extras Menu Forum Themes Elegant Mobile Home » All Forums » [16
Gdb Cannot Access Memory At Address
bit Microcontrollers & Digital Signal controllers] » PIC24 Topics » PIC24E Address Error Trap accessing > 0x8000 pointer [SOLVED] Mark Thread UnreadFlat Reading Mode❐ PIC24E Address Error Trap accessing > 0x8000 pointer [SOLVED] Author Post Essentials Only Full Version alessandromelio New Member Total Posts : 5 Reward points : 0 Joined: 2012/01/19 07:11:30Location: 0 Status: offline 2012/11/23 03:54:13 (permalink) 0 PIC24E Address Error Trap accessing > 0x8000 pointer [SOLVED] https://sourceware.org/bugzilla/show_bug.cgi?id=8953 Hi all I'm using a PIC24EP512GU810 with USB and MDD file system Microchip library. Compiler version is 3.31. When I call the FindFirst() function (from FSIO library) passing a constant filename FindFirst("*.*", ATTR_VOLUME, &searchRecord )) the function calls FormatFileName passing the pointer to the "*.*" string. FormatFileName(fileName, fo, 1) but when checking the length of file name, there is an address error trap. Breacking execution before the trap, http://www.microchip.com/forums/m689581.aspx I found that the fileName pointer points to a location placed at 0x9272. If I well understood the PSV mechanism, pointing to an area outside 0x8000 without managing all the PSV stuff (__psv__ or DSRPAG, etc) can cause an address error trap. I don't think it's a library bug, but maybe I miss some compiler/linker setting or there is something to add to the code in order to manage a case like this. I compile the code with -mconst-in-code -mlarge-code -mlarge-data options and optimization at 's'. Any suggestion? If can help, this is my map: Program Memory [Origin = 0x2008, Length = 0x537f8] section address length (PC units) length (bytes) (dec) ------- ------- ----------------- -------------------- _027fc2a050af5143 0x2008 0x6 0x9 (9) _027fc15050af5143 0x200e 0x6 0x9 (9) _027fc3f050af5143 0x2014 0x6 0x9 (9) _025af8c050af5141 0x201a 0x2 0x3 (3) _025af69050af5141 0x201c 0x2 0x3 (3) .text 0x201e 0x14 0x1e (30) _03b4f85050af513c 0x204c 0x6 0x9 (9) _03d6fbd050af5152 0x2052 0x6 0x9 (9) _03b508c050af5150 0x2058 0x6 0x9 (9) _03b50c4050af5150 0x205e 0x6 0x9 (9) _03b5100050af5150 0x2064 0x6 0x9 (9) _03c3770050af5133 0x206a 0x6 0x9 (9) .text 0x2070 0x1eba 0x2e17 (11799) _025afc4050af5141 0x3f2a 0x2800 0x3c00 (15360) .const 0x672a 0xd38 0x13d4 (5076) _03b9f4d050af5148 0x7462 0x3bc 0x59a (1434) _03b9f38050af5148 0x781e 0x27e 0x3bd (957) .text 0x7a9c 0x7436 0xae51 (44625
and End-of-Life ProductsCisco IOS Software Releases 12.1 MainlineTroubleshoot and AlertsTroubleshooting TechNotes Troubleshooting Bus Error Crashes Download Print Available Languages Download Options PDF (153.3 KB) View with Adobe Reader on a http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/7949-crashes-buserror-troubleshooting.html variety of devices ePub (111.5 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone Mobi (Kindle) (129.9 KB) View on Kindle device or Kindle app on multiple devices Updated:Jun 16, 2016 Document ID:7949 ContentsIntroductionPrerequisitesRequirementsComponents UsedConventionsIdentifying Bus Error CrashesTroubleshooting Bus Error CrashesTroubleshooting Bus Error Crashes on 68000 Processor PlatformsTroubleshooting Bus Error Crashes on RISC Processor PlatformsSpecial Types of Bus Error CrashesTroubleshooting Techniques for cannot access Bus Error Exception Boot LoopsCisco IOS Software Loaded Does Not Support Installed HardwareSoftware FailureMis-seated HardwareHardware FailureInformation to Collect if You Open a Service RequestRelated Information Introduction This document explains how to identify bus error crashes and how to troubleshoot those crashes depending on the type of processor you have in your Cisco router. Prerequisites Requirements Cisco recommends that you read Troubleshooting Router Crashes before proceeding with this document. cannot access memory Components Used The information in this document is based on these software and hardware versions: All Cisco IOSĀ® software versions All Cisco routers Note:This document does not apply to Cisco Catalyst switches or MGX platforms. The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to the Cisco Technical Tips Conventions for more information on document conventions. Identifying Bus Error Crashes The system encounters a bus error when the processor tries to access a memory location that either does not exist (a software error) or does not respond properly (a hardware problem). A bus error can be identified from the output of the show version command provided by the router if not power-cycled or manually reloaded. If you have the output of a show version or show technical-support command (from enable mode) from your Cisco device, you can use it to display potential issues and fixes. In order to use it, you must be a registered customer, be logged in, and have Java