Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: Alpha completely broken: build_regcache never called
Date: Fri, 05 Apr 2002 18:39:00 -0000	[thread overview]
Message-ID: <20020405213936.A22001@nevyn.them.org> (raw)
In-Reply-To: <3CAE5DCB.7080102@cygnus.com>

On Fri, Apr 05, 2002 at 09:30:35PM -0500, Andrew Cagney wrote:
> >That function only initializes things created with
> >>>register_gdbarch_data... not register_gdbarch_swap.  Adding a call to
> >>>init_gdbarch_swap (&startup_gdbarch) in initialize_non_multiarch causes
> >>>it to be called.  Is that correct?
> >
> >>
> >>Er, yes :-(  Does it ``work'' (between the other two functions to match 
> >>gdbarch_update_p())?
> >
> >
> >Yep.  Want me to check it in?
> 
> M'kay (thanks).  No need for the branch - doesn't contain the patch that 
> triggered this.

Sure.  I committed this.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.2382
diff -u -r1.2382 ChangeLog
--- ChangeLog	2002/04/06 01:52:34	1.2382
+++ ChangeLog	2002/04/06 02:37:45
@@ -1,3 +1,8 @@
+2002-04-05  Daniel Jacobowitz  <drow@mvista.com>
+
+	* gdbarch.sh (initialize_non_multiarch): Call init_gdbarch_swap.
+	* gdbarch.c: Regenerate.
+
 2002-04-05  Michael Snyder  <msnyder@redhat.com>
 
 	* cli/cli-dump.c (restore_section_callback): Use paddr_nz.
Index: gdbarch.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.c,v
retrieving revision 1.111
diff -u -r1.111 gdbarch.c
--- gdbarch.c	2002/03/19 02:51:05	1.111
+++ gdbarch.c	2002/04/06 02:37:46
@@ -412,6 +412,7 @@
 initialize_non_multiarch ()
 {
   alloc_gdbarch_data (&startup_gdbarch);
+  init_gdbarch_swap (&startup_gdbarch)
   init_gdbarch_data (&startup_gdbarch);
 }
 
Index: gdbarch.sh
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.sh,v
retrieving revision 1.119
diff -u -r1.119 gdbarch.sh
--- gdbarch.sh	2002/03/19 02:51:07	1.119
+++ gdbarch.sh	2002/04/06 02:37:47
@@ -1333,6 +1333,7 @@
 initialize_non_multiarch ()
 {
   alloc_gdbarch_data (&startup_gdbarch);
+  init_gdbarch_swap (&startup_gdbarch)
   init_gdbarch_data (&startup_gdbarch);
 }
 EOF


      reply	other threads:[~2002-04-06  2:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 15:05 Daniel Jacobowitz
2002-04-03 15:23 ` Martin M. Hunt
2002-04-03 21:15 ` Andrew Cagney
2002-04-03 21:25   ` Daniel Jacobowitz
2002-04-04  6:23     ` Andrew Cagney
2002-04-04  8:42       ` Daniel Jacobowitz
2002-04-05 18:30         ` Andrew Cagney
2002-04-05 18:39           ` Daniel Jacobowitz [this message]

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=20020405213936.A22001@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@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