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: Paul Pluzhnikov <ppluzhnikov@google.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch] Fix a reread_symbols regression by mmap  [Re: [patch] Use 	mmap instead of obstack_alloc for dwarf debug   sections.]
Date: Tue, 23 Jun 2009 18:08:00 -0000	[thread overview]
Message-ID: <m3ab3ylt5i.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090623150322.GA7654@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue\, 23 Jun 2009 17\:03\:22 +0200")

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

Jan> while sure your patch is great it has a regression.  Assuming a regression
Jan> reproducer needs to link GDB with -lmcheck (but did verify it).

Thanks for finding this.

Jan> 2009-06-23  Jan Kratochvil  <jan.kratochvil@redhat.com>
Jan> 	Fix a regression by the mmap patch from 2009-06-16.
Jan> 	* symfile.c (reread_symbols): Move sym_finish and clear_objfile_data
Jan> 	calls before deleting the OBJFILE obstack.  Extend the comment.

This is ok.

Jan> +		 Try to keep the freeing order compatible with free_objfile.  */

It seems like it would be nice to have a single function here.

Tom


  parent reply	other threads:[~2009-06-23 18:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  0:12 [patch] Use mmap instead of obstack_alloc for dwarf debug sections Paul Pluzhnikov
2009-05-28  1:16 ` Tom Tromey
2009-05-28 16:57   ` Paul Pluzhnikov
2009-05-30 22:36     ` Tom Tromey
2009-06-11  1:40       ` Paul Pluzhnikov
2009-06-11  1:43         ` Paul Pluzhnikov
2009-06-16 19:19           ` Tom Tromey
2009-06-16 20:43             ` Paul Pluzhnikov
2009-06-16 20:59               ` Tom Tromey
2009-06-16 21:07                 ` Paul Pluzhnikov
2009-06-18  9:20                   ` Ken Werner
2009-06-18 14:06                     ` Paul Pluzhnikov
2009-06-18 14:11                       ` Paul Pluzhnikov
2009-06-18 15:02                       ` Ken Werner
2009-06-18 16:33                         ` Paul Pluzhnikov
2009-06-19  7:10                           ` Ken Werner
2009-06-23 15:03                   ` [patch] Fix a reread_symbols regression by mmap [Re: [patch] Use mmap instead of obstack_alloc for dwarf debug sections.] Jan Kratochvil
2009-06-23 17:35                     ` Paul Pluzhnikov
2009-06-23 18:08                     ` Tom Tromey [this message]
2009-06-23 18:21                       ` Jan Kratochvil
2009-06-23 20:00                         ` Tom Tromey
2009-06-25 19:21                           ` [patch] Replace reread_symbols by load+free calls Jan Kratochvil
2009-06-25 19:57                             ` Pedro Alves
2009-06-25 23:25                               ` Jan Kratochvil
2009-08-02 21:04                                 ` cancelled: " Jan Kratochvil
2009-08-14 23:09                             ` Tom Tromey
2009-08-14 23:12                               ` Pedro Alves
2009-08-17 15:41                                 ` Tom Tromey
2011-12-18 11:54                                 ` 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=m3ab3ylt5i.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jan.kratochvil@redhat.com \
    --cc=ppluzhnikov@google.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