From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb] Fix gdb crash when reading core file
Date: Tue, 06 Nov 2018 15:40:00 -0000 [thread overview]
Message-ID: <87k1lqrz8y.fsf@tromey.com> (raw)
In-Reply-To: <20181101130549.GA31366@delia> (Tom de Vries's message of "Thu, 1 Nov 2018 14:05:50 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> 2018-11-01 Tom de Vries <tdevries@suse.de>
Tom> * linux-tdep.c (linux_vsyscall_range_raw): Use xmalloc to allocate
Tom> program headers.
Tom> * gdb.base/many-headers.c: New test.
Tom> * gdb.base/many-headers.exp: New file.
Thanks for the patch.
This looks good. However, I think the new .c file should have a
copyright header. This is ok with that change.
Tom
prev parent reply other threads:[~2018-11-06 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 13:05 Tom de Vries
2018-11-06 15:40 ` Tom Tromey [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=87k1lqrz8y.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.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