Error Accessing Memory Address 0x1 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
Gdb Cannot Insert Breakpoint 0
other bugs) Version: 6.3 Importance: P2 critical Target Milestone: --- Assignee: Not yet gdb cannot access memory at address assigned to anyone URL: Keywords: Depends on: Blocks: Reported: 2005-01-20 02:28 UTC 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
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, https://sourceware.org/bugzilla/show_bug.cgi?id=8953 recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Assembly http://www.tek-tips.com/viewthread.cfm?qid=819059 Forum at Tek-Tips HomeForumsProgrammersLanguagesAssembly Forum Syscall problem thread272-819059 Forum Search FAQs Links MVPs Syscall problem Syscall problem keratox (Programmer) (OP) 10 Apr 04 16:40 Hi all,the problem is that my program produces a segmentation fault but I don't know why, but the strange thing is that when I use gdb and I set a breakpoint to a specific line of the code, the program terminates correctly!Here's the code:global mainmain:lea esi,[sh]xor eax,eax;syscall execve("/bin/sh")mov byte[esi+7],$0mov [esi+8],esimov [esi+0xc],eaxlea edx,[esi+0xc]lea ecx,[esi+0x8]mov ebx,esimov al,0xb;1° breakpoint(If i set a break here the program terminates normally)int 0x80xor eax, eax;syscall exit(0)xor ebx, ebxinc eaxint 0x80.datash db'/bin/sh';As you can see, this code issues an execve("/bin/sh"..) syscall which spawns a shell, but it produces a segmentation fault at run-time.Debugging with gdb I got this error, that looks like eip is overwritten by something (eip points to 0x40000bb0 but it shouldn't!!):Program received signal SIGTRAP, Trace/breakpoint trap.0x40000bb0 in ?? ()But when
Date: Tue, 2 Dec 2003 15:48:02 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=222726;msg=5 UTC Severity: normal Found in version 3.1r-4 Fixed in version xaos/3.1r-5 Done: Joey Hess
linux function calls. I am able to debug as long as I don't set any breakpoints or try to single step over some linux function calls. This is the output in the console window I see when I try to debug my program: Stopped due to shared library event [Thread debugging using libthread_db enabled] [New Thread -1209764176 (LWP 27866)] Stopped due to shared library event [Switching to Thread -1209764176 (LWP 27866)] Stopped due to shared library event I can still debug, however as long as I don't try to break on or single step over certain function calls. Here is what happens if I try to step over (not into) getservbyname system call, things go very bad: Warning: Cannot insert breakpoint 0. Error accessing memory address 0x1: Input/output error. Single stepping until exit from function _dl_debug_state, which has no line number information. No symbol "protocol" in current context. I searched through this forum and on the web but found nothing that seemed to match my problem. Here is my system information: OS: ubuntu 7.10 running on VMware Workstation 6.0.2 build-59824 Eclipse: Version: 3.3.1.1 Build id: M20071023-1652 CDT SDK 4.0.0 Any help would be greatly appreciated. Thanks, Iztok View this message in context: Single stepping until exit from function _dl_debug_state... Sent from the Eclipse CDT - debug mailing list archive at Nabble.com. _______________________________________________ cdt-debug-dev mailing list cdt-debug-dev-j9T/66MeVpFAfugRpC6u6w@xxxxxxxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev Thread at a glance: Previous Message by Date: Re: GDB launching source paths issue. Thanks for your tip! I will have a shot at it...Brgds,Marcus2008/3/13 Elena Laskavaia