From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix crash on stale addrinfo->sectindex
Date: Fri, 19 Feb 2010 03:10:00 -0000 [thread overview]
Message-ID: <m3635tc449.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100218092203.GA31309@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Thu, 18 Feb 2010 10:22:03 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> 2010-02-18 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> * symfile.c (addr_info_make_relative): Extend comment. Move SECT to
Jan> a more inner block. Initialize ADDR by LOWER_OFFSET only if it was
Jan> found by bfd_get_section_by_name.
Jan> * symfile.h (struct section_addr_info) <sectindex>: New comment.
Oh, by the way, I think this is reasonable for 7.1. It is
straightforward and fixes a reported crash. If Joel agrees, please put
it on the branch. Thanks.
Tom
prev parent reply other threads:[~2010-02-19 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 9:22 Jan Kratochvil
2010-02-19 3:01 ` Tom Tromey
2010-02-19 6:22 ` Jan Kratochvil
2010-02-19 13:16 ` Joel Brobecker
2010-02-19 14:07 ` Jan Kratochvil
2010-02-19 3:10 ` 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=m3635tc449.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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