From: Gaius Mulley <gaius@glam.ac.uk>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org, drow@false.org
Subject: Re: recursive bug in dwarf2read.c
Date: Wed, 16 Dec 2009 15:14:00 -0000 [thread overview]
Message-ID: <87hbrr6jdp.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <m3iqcdxlti.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri\, 11 Dec 2009 14\:06\:17 -0700")
Tom Tromey <tromey@redhat.com> writes:
>>>>>> "Gaius" == Gaius Mulley <gaius@glam.ac.uk> writes:
>
> Gaius> ahh yes - true, here is the modified patch without the redundant
> Gaius> second call:
>
> Thanks, this is ok.
>
> Tom
Hi Tom,
many thanks, now committed to the head cvs,
regards,
Gaius
2009-12-15 Gaius Mulley <gaius@glam.ac.uk>
* dwarf2read.c (read_subroutine_type): Add the subroutine
type to the die immediately to allow a parameter type to be
the same subroutine type.
prev parent reply other threads:[~2009-12-16 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878wdcto0t.fsf@j228-gm.comp.glam.ac.uk>
[not found] ` <20091209185157.GA29691@caradoc.them.org>
2009-12-10 19:39 ` Gaius Mulley
2009-12-11 19:29 ` Tom Tromey
2009-12-11 20:56 ` Gaius Mulley
2009-12-11 21:06 ` Tom Tromey
2009-12-16 15:14 ` Gaius Mulley [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=87hbrr6jdp.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius@glam.ac.uk \
--cc=drow@false.org \
--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