Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Tristan Gingold <gingold@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [patch] build_section_addr_info* SEC_ALLOC/SEC_LOAD unification
Date: Wed, 17 Feb 2010 19:04:00 -0000	[thread overview]
Message-ID: <m3ljerfzus.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100213223425.GA27252@host0.dyn.jankratochvil.net> (Jan 	Kratochvil's message of "Sat, 13 Feb 2010 23:34:25 +0100")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> 2010-02-13  Jan Kratochvil  <jan.kratochvil@redhat.com>
Jan> 	* symfile.c (build_section_addr_info_from_objfile): Include sections
Jan> 	only if they are SEC_ALLOC or SEC_LOAD.

This is ok.  Thanks.  And thanks, Tristan, for looking at it.

Tom


  parent reply	other threads:[~2010-02-17 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-13 22:34 Jan Kratochvil
2010-02-17  8:51 ` Tristan Gingold
2010-02-17 19:04 ` Tom Tromey [this message]
2010-02-17 20:55   ` Jan Kratochvil

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=m3ljerfzus.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.com \
    --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