From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: kettenis@chello.nl, gdb-patches@gcc.gnu.org, cagney@gnu.org
Subject: Re: [PATCH/RFC] Per-architecture DWARF CFI register state initialization hooks
Date: Mon, 16 Feb 2004 19:47:00 -0000 [thread overview]
Message-ID: <20040216194731.GC1819@nevyn.them.org> (raw)
In-Reply-To: <200402161301.OAA17984@faui1d.informatik.uni-erlangen.de>
On Mon, Feb 16, 2004 at 02:01:29PM +0100, Ulrich Weigand wrote:
> Daniel Jacobowitz wrote:
>
> > On Mon, Feb 16, 2004 at 02:27:24AM +0100, Ulrich Weigand wrote:
> > > +void
> > > +dwarf2_frame_set_init_reg (struct gdbarch *gdbarch,
> > > + void (*init_reg) (struct gdbarch *, int,
> > > + struct dwarf2_frame_state_reg *))
> >
> > > Unfortunately this now crashes on s390, because the
> > > dwarf2_frame_init routine is called from within
> > > _initialize_dwarf2_frame, while the s390 backend calls
> > > dwarf2_frame_set_init_reg from within _initialize_s390_tdep.
> >
> > Er, how? You shouldn't have a gdbarch in _initialize_s390_tdep. You
> > don't have one until s390_gdbarch_init.
>
> Sorry, my analysis wasn't completely correct. What actually happens
> is an init-order problem during the initialization of the gdbarch
> in initialize_current_architecture. The problem is that I call
> dwarf2_frame_set_init_reg from within the s390_gdbarch_init routine
> (which I gather is the right place?), and at this point in time,
> the gdbarch_data call in dwarf2_frame_set_init_reg returns NULL
> because the gdbarch hasn't finished initialization yet:
>
> gdbarch_data (struct gdbarch *gdbarch, struct gdbarch_data *data)
> {
> gdb_assert (data->index < gdbarch->nr_data);
> /* The data-pointer isn't initialized, call init() to get a value but
> only if the architecture initializaiton has completed. Otherwise
> punt - hope that the caller knows what they are doing. */
> if (gdbarch->data[data->index] == NULL
> && gdbarch->initialized_p)
Oopsie. Yes, now I can see what's going on - I'm not sure what should
change here. Andrew, do you recall if the initialized_p check was for
any specific problem, or might we be able to remove it?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-16 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 1:28 Ulrich Weigand
2004-02-16 1:56 ` Daniel Jacobowitz
2004-02-16 13:01 ` Ulrich Weigand
2004-02-16 19:47 ` Daniel Jacobowitz [this message]
2004-02-16 20:50 ` Andrew Cagney
2004-02-16 20:55 ` Andrew Cagney
2004-02-18 16:59 ` Mark Kettenis
2004-02-18 18:40 ` Andrew Cagney
2004-02-16 21:31 ` [PATCH/RFC] Per-architecture DWARF CFI register state initialization Ulrich Weigand
-- strict thread matches above, loose matches on Subject: below --
2004-02-07 22:38 [PATCH/RFC] Per-architecture DWARF CFI register state initialization hooks Mark Kettenis
2004-02-07 23:03 ` Daniel Jacobowitz
2004-02-07 23:48 ` Andrew Cagney
2004-02-15 15:31 ` Mark Kettenis
2004-02-15 16:04 ` Andrew Cagney
2004-02-15 18:09 ` Daniel Jacobowitz
2004-02-15 19:49 ` Andrew Cagney
2004-02-15 20:37 ` Daniel Jacobowitz
2004-02-15 21:37 ` Andrew Cagney
2004-02-15 22:54 ` Daniel Jacobowitz
2004-02-15 21:31 ` Mark Kettenis
2004-02-08 1:01 ` Ulrich Weigand
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=20040216194731.GC1819@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=kettenis@chello.nl \
--cc=weigand@i1.informatik.uni-erlangen.de \
/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