From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] frame_id_unwind()
Date: Fri, 13 Dec 2002 12:21:00 -0000 [thread overview]
Message-ID: <ork7idu0ut.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <3DF7A9EE.3080908@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On Dec 11, 2002, Andrew Cagney <ac131313@redhat.com> wrote:
> +struct frame_id
^^
> +dummy_frame_id_unwind (struct frame_info *frame,
> + void **cache)
> +extern struct frame_id dummy_frame_id_unwind (struct frame_info *frame,
> + void **unwind_cache);
> +
^^
> +struct frame_id
> +frame_id_unwind (struct frame_info *frame)
> +{
> + if (!frame->id_unwind_cache_p)
> + {
> + frame->id_unwind_cache =
> + frame->id_unwind (frame, &frame->unwind_cache);
[ type mismatch above ]
> + frame->id_unwind_cache_p = 1;
> + }
> + return frame->id_unwind_cache;
> +}
> +/* Unwind the frame ID. Return an ID that uniquely identifies the
> + caller's frame. */
> +extern struct frame_id frame_id_unwind (struct frame_info *frame);
^^
> + struct frame_id id_unwind_cache;
^^
I believe this is enough evidence that the typedef below was meant to
have struct frame_id in the return type, instead of frame_info:
> +typedef struct frame_info (frame_id_unwind_ftype) (struct frame_info *frame,
> + void **unwind_cache);
^^^^
So I'm checking this in as obvious.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gdb-frame-id-unwind-ret-type.patch --]
[-- Type: text/x-patch, Size: 820 bytes --]
Index: gdb/ChangeLog
from Alexandre Oliva <aoliva@redhat.com>
* frame.h (frame_id_unwind_ftype): Fix typo in return type.
Index: gdb/frame.h
===================================================================
RCS file: /cvs/uberbaum/gdb/frame.h,v
retrieving revision 1.49
diff -u -p -r1.49 frame.h
--- gdb/frame.h 13 Dec 2002 16:40:25 -0000 1.49
+++ gdb/frame.h 13 Dec 2002 20:14:23 -0000
@@ -335,8 +335,8 @@ typedef CORE_ADDR (frame_pc_unwind_ftype
/* Same as for registers above, but return the ID of the frame that
called this one. */
-typedef struct frame_info (frame_id_unwind_ftype) (struct frame_info *frame,
- void **unwind_cache);
+typedef struct frame_id (frame_id_unwind_ftype) (struct frame_info *frame,
+ void **unwind_cache);
/* Describe the saved registers of a frame. */
[-- Attachment #3: Type: text/plain, Size: 289 bytes --]
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-12-13 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 13:14 Andrew Cagney
2002-12-13 8:50 ` Andrew Cagney
2002-12-13 12:21 ` Alexandre Oliva [this message]
2002-12-13 12:38 ` Andrew Cagney
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=ork7idu0ut.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=ac131313@redhat.com \
--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