Article View: gnu.gdb.bug
Article #259read_memory bug
From: Bryan Boreham
Date: Sun, 17 Sep 1989 14:35
Date: Sun, 17 Sep 1989 14:35
24 lines
923 bytes
923 bytes
This code in core.c contains an error:
int
read_memory (memaddr, myaddr, len)
CORE_ADDR memaddr;
char *myaddr;
int len;
{
if (len == 0)
return; <---- return what?
if (have_inferior_p ())
return read_inferior_memory (memaddr, myaddr, len);
else
return xfer_core_file (memaddr, myaddr, len);
}
I'd say it should return 0.
This sometimes causes gdb to report that ptrace got an "unknown error"
when you try to print *p when p is declared like "struct foobar *p;".
Bryan.
Technical Details
Message-ID:
<8909171435.AA19422@edinburgh.kewill.uucp>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!UUNET.UU.NET!kewill!bryanShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!UUNET.UU.NET!kewill!bryan From: kewill!bryan@UUNET.UU.NET (Bryan Boreham) Newsgroups: gnu.gdb.bug Subject: read_memory bug Message-ID: <8909171435.AA19422@edinburgh.kewill.uucp> Date: 17 Sep 89 14:35:59 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 24