Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Entry point update with "run" command
Date: Mon, 05 May 2008 19:17:00 -0000	[thread overview]
Message-ID: <1210004084.25903.0.camel@gargoyle> (raw)
In-Reply-To: <20080502154355.GQ29202@caradoc.them.org>

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

I've checked this in now. Thanks!

On Fri, 2008-05-02 at 11:43 -0400, Daniel Jacobowitz wrote:
> On Thu, Apr 24, 2008 at 12:58:14PM -0300, Luis Machado wrote:
> > The attached patch does this on "reread_symbols", though it seems a
> > brute-force method. Is this OK?
> 
> This is OK.  Wow, this function is a wreck.  Despite the comments it
> really does need to be updated to share code with initial reading of
> the symfile at some point.
> 

Luis


[-- Attachment #2: entry_point.diff --]
[-- Type: text/x-patch, Size: 521 bytes --]

2008-05-05  Luis Machado  <luisgpm@br.ibm.com>

	* symfile.c (reread_symbols): Update objfile's entry point.

Index: HEAD/gdb/symfile.c
===================================================================
--- HEAD.orig/gdb/symfile.c	2008-05-05 05:27:16.000000000 -0700
+++ HEAD/gdb/symfile.c	2008-05-05 05:31:54.000000000 -0700
@@ -2474,6 +2474,7 @@
 	      objfile->mtime = new_modtime;
 	      reread_one = 1;
               reread_separate_symbols (objfile);
+	      init_entry_point_info (objfile);
 	    }
 	}
     }

      reply	other threads:[~2008-05-05 16:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 16:45 Luis Machado
2008-04-26 13:42 ` Jan Kratochvil
2008-05-01 16:19   ` Luis Machado
2008-05-02 15:46   ` Daniel Jacobowitz
2008-05-04 15:23     ` Jan Kratochvil
2008-05-02 15:45 ` Daniel Jacobowitz
2008-05-05 19:17   ` Luis Machado [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=1210004084.25903.0.camel@gargoyle \
    --to=luisgpm@linux.vnet.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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