This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [commit] Fix info frame's saved registers output
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Andrew Cagney <cagney at gnu dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sun, 31 Oct 2004 01:01:11 +0200
- Subject: Re: [commit] Fix info frame's saved registers output
- References: <41824D61.3050208@gnu.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 29 Oct 2004 10:02:09 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> 2004-10-27 Andrew Cagney <cagney@gnu.org>
>
> * trad-frame.c (trad_frame_get_prev_register): Use
> frame_unwind_register instead of frame_register_unwind
Isn't it confusing to have 2 different functions whose names are just
permutations of the same words? How can a GDB hacker know what is the
difference between frame_register_unwind and frame_unwind_register,
without reading the sources?