Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: restore accidentally deleted call
Date: Fri, 11 Apr 2003 19:01:00 -0000	[thread overview]
Message-ID: <vt2smsooo12.fsf@zenia.red-bean.com> (raw)


The call below was deleted in revision 1.88 of s390-tdep.c; inferior
calls broke because they didn't return to the call dummy breakpoint.
Since the ChangeLog entry only talks about deleting the gdbarch calls
to set CALL_DUMMY_START_OFFSET and CALL_DUMMY_LENGTH, I'm guessing
that was by accident.

2003-04-10  Jim Blandy  <jimb@redhat.com>

	* s390-tdep.c (s390_gdbarch_init): Put back accidentally deleted
	call to set_gdbarch_deprecated_push_arguments.

Index: s390-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/s390-tdep.c,v
retrieving revision 1.89
diff -c -r1.89 s390-tdep.c
*** s390-tdep.c	5 Apr 2003 18:54:38 -0000	1.89
--- s390-tdep.c	10 Apr 2003 22:26:56 -0000
***************
*** 1864,1869 ****
--- 1864,1871 ----
    set_gdbarch_deprecated_pc_in_call_dummy (gdbarch, deprecated_pc_in_call_dummy_at_entry_point);
    set_gdbarch_deprecated_push_arguments (gdbarch, s390_push_arguments);
    set_gdbarch_save_dummy_frame_tos (gdbarch, generic_save_dummy_frame_tos);
+   set_gdbarch_deprecated_push_return_address (gdbarch,
+                                               s390_push_return_address);
    set_gdbarch_sizeof_call_dummy_words (gdbarch,
                                         sizeof (s390_call_dummy_words));
    set_gdbarch_call_dummy_words (gdbarch, s390_call_dummy_words);


             reply	other threads:[~2003-04-11 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 19:01 Jim Blandy [this message]
2003-04-11 20:14 ` 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=vt2smsooo12.fsf@zenia.red-bean.com \
    --to=jimb@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