From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [ia64] No start when GDB built with -lmcheck
Date: Tue, 25 Aug 2009 14:18:00 -0000 [thread overview]
Message-ID: <20090825140959.GA12707@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3k512i92k.fsf@fleche.redhat.com>
On Mon, 17 Aug 2009 20:33:55 +0200, Tom Tromey wrote:
> I think if you go this route, you should remove the redundant
> initializations a couple lines down:
[...]
> Either approach is pre-approved.
I see I was too quick, checked it in with xzalloc.
Only simple ia64-rhel5-linux-gnu run was made.
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2009-08/msg00122.html
--- src/gdb/ChangeLog 2009/08/25 00:23:06 1.10824
+++ src/gdb/ChangeLog 2009/08/25 14:06:44 1.10825
@@ -1,3 +1,10 @@
+2009-08-25 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ Fix ia64 start crash when GDB built with -lmcheck.
+ * ia64-tdep.c (ia64_gdbarch_init): Allocate TDEP as cleared. Remove
+ specific clearing of TDEP SIGCONTEXT_REGISTER_ADDRESS and
+ PC_IN_SIGTRAMP.
+
2009-08-24 Keith Seitz <keiths@redhat.com>
* c-exp.y (tokentab3): Add new token, ARROW_STAR. Changed all users.
--- src/gdb/ia64-tdep.c 2009/07/30 16:29:53 1.195
+++ src/gdb/ia64-tdep.c 2009/08/25 14:06:47 1.196
@@ -3671,12 +3671,9 @@
if (arches != NULL)
return arches->gdbarch;
- tdep = xmalloc (sizeof (struct gdbarch_tdep));
+ tdep = xzalloc (sizeof (struct gdbarch_tdep));
gdbarch = gdbarch_alloc (&info, tdep);
- tdep->sigcontext_register_address = 0;
- tdep->pc_in_sigtramp = 0;
-
/* According to the ia64 specs, instructions that store long double
floats in memory use a long-double format different than that
used in the floating registers. The memory format matches the
prev parent reply other threads:[~2009-08-25 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 21:19 Jan Kratochvil
2009-08-17 18:50 ` Tom Tromey
2009-08-25 14:18 ` Jan Kratochvil [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=20090825140959.GA12707@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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