From: Mark Kettenis <kettenis@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [COMMIT] Some amd64-linux-tdep.c tweaks
Date: Wed, 16 Feb 2005 06:43:00 -0000 [thread overview]
Message-ID: <200502160217.j1G2HZ7O019126@copland.sibelius.xs4all.nl> (raw)
Committed,
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* amd64-linux-tdep.c: Update copyright year.
(amd64_linux_sigtramp_start): Change argument to `struct
frame_info *'. Use safe_frame_unwind_memory instead of
deprecated_read_memory_nobpt.
(amd64_linux_sigtramp_p): Adjust call to
amd64_linux_sigtramp_start.
Index: amd64-linux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/amd64-linux-tdep.c,v
retrieving revision 1.7
diff -u -p -r1.7 amd64-linux-tdep.c
--- amd64-linux-tdep.c 22 Aug 2004 16:27:30 -0000 1.7
+++ amd64-linux-tdep.c 16 Feb 2005 02:15:20 -0000
@@ -1,6 +1,6 @@
/* Target-dependent code for GNU/Linux x86-64.
- Copyright 2001, 2003, 2004 Free Software Foundation, Inc.
+ Copyright 2001, 2003, 2004, 2005 Free Software Foundation, Inc.
Contributed by Jiri Smid, SuSE Labs.
This file is part of GDB.
@@ -98,7 +98,7 @@ amd64_linux_sigtramp_start (struct frame
PC is not at the start of the instruction sequence, there will be
a few trailing readable bytes on the stack. */
- if (!safe_frame_unwind_memory (next_frame, pc, buf, LINUX_SIGTRAMP_LEN))
+ if (!safe_frame_unwind_memory (next_frame, pc, buf, sizeof buf))
return 0;
if (buf[0] != LINUX_SIGTRAMP_INSN0)
@@ -107,8 +107,7 @@ amd64_linux_sigtramp_start (struct frame
return 0;
pc -= LINUX_SIGTRAMP_OFFSET1;
-
- if (!safe_frame_unwind_memory (next_frame, pc, buf, LINUX_SIGTRAMP_LEN))
+ if (!safe_frame_unwind_memory (next_frame, pc, buf, sizeof buf))
return 0;
}
next reply other threads:[~2005-02-16 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 6:43 Mark Kettenis [this message]
2005-02-16 13:04 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200502160217.j1G2HZ7O019126@copland.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox