From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix a symbol_file_clear crash regression
Date: Tue, 27 Apr 2010 17:33:00 -0000 [thread overview]
Message-ID: <m3aasoiyws.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100426145108.GA9357@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Mon, 26 Apr 2010 16:51:08 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> 2010-04-26 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> * objfiles.c: Include solist.h.
Jan> (free_all_objfiles): New variable so. Check stale solist objfiles.
Jan> * symfile.c (symbol_file_clear): Swap the order of free_all_objfiles
Jan> and no_shared_libraries.
This is ok. Thanks.
Tom
next prev parent reply other threads:[~2010-04-27 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 14:51 Jan Kratochvil
2010-04-27 17:33 ` Tom Tromey [this message]
2010-04-27 20:07 ` 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=m3aasoiyws.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).