Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Joel Sherrill <joel.sherrill@oarcorp.com>,
	        "gdb@sourceware.org" <gdb@sourceware.org>,
	        Ralf Corsepius <ralf.corsepius@rtems.org>,
	gdb-patches@sourceware.org
Subject: Re: SPARC GDB Failure
Date: Mon, 07 Sep 2009 18:35:00 -0000	[thread overview]
Message-ID: <20090907183532.GA17150@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <e394668d0909071115p4fa41d15u13db897df9bf351b@mail.gmail.com>

On Mon, 07 Sep 2009 20:15:46 +0200, Doug Evans wrote:
> Long-term-wise, maybe the thing to do is have all allocs of
> gdbarch_tdep go through a function (gdbarch_tdep_alloc or some such).
> That would make it clear how one *should* alloc them.

I do not find any functions outside of the target file(s) to depend on its
fields (they cannot, the structure is opaque to them, as Joel has said).

I would find such change the same as changing xmalloc to always do xzalloc.
At least for mn10300 such change would be excessive.

(I would find OK to put xzalloc there but I do not find it right by design.)


Thanks,
Jan


  parent reply	other threads:[~2009-09-07 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AA5161D.1020102@oarcorp.com>
2009-09-07 16:45 ` Jan Kratochvil
2009-09-07 17:44   ` Doug Evans
2009-09-07 17:54     ` Jan Kratochvil
2009-09-07 18:16       ` Doug Evans
2009-09-07 18:24         ` Joel Brobecker
2009-09-07 18:35         ` Jan Kratochvil [this message]
2009-09-07 18:40         ` Joel Sherrill
2009-09-08  6:46           ` Ralf Corsepius

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=20090907183532.GA17150@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=joel.sherrill@oarcorp.com \
    --cc=ralf.corsepius@rtems.org \
    /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