Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: Roger Sayle <roger@eyesopen.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PING] 13 months and counting for PR symtab/1651 fix.
Date: Mon, 02 Jan 2006 05:52:00 -0000	[thread overview]
Message-ID: <8f2776cb0601012151y30cf2672i8b32f958f605a982@mail.gmail.com> (raw)
In-Reply-To: <8f2776cb0601012033h738f5983g9dc7450caffa8a88@mail.gmail.com>

On 1/1/06, Jim Blandy <jimb@red-bean.com> wrote:
> On 12/30/05, Roger Sayle <roger@eyesopen.com> wrote:
> > Being the season of good-will, is there any chance some kind soul
> > could commit this fix to CVS, and thereby close "serious" bug
> > symtab/1651 in gdb's bug database?
>
> I've committed Elena's patch, and closed the bug.  Happy New Year!

Here's what I actually committed:


gdb/ChangeLog:
2006-01-01  Roger Sayle  <roger@eyesopen.com>
            Elena Zannoni <ezannoni@redhat.com>

	PR symtab/1651
	* xcoffread.c (xcoff_next_symbol_text): Check this_symtab_psymtab
	for NULL before assigning this_symtab_psymtab->objfile to objfile.
	(scan_xcoff_symtab): Initialize next_symbol_text_func.
        (Committed by Jim Blandy)

Index: gdb/xcoffread.c
===================================================================
RCS file: /cvs/src/src/gdb/xcoffread.c,v
retrieving revision 1.47
diff -c -p -r1.47 xcoffread.c
*** gdb/xcoffread.c	17 Dec 2005 22:34:03 -0000	1.47
--- gdb/xcoffread.c	2 Jan 2006 04:30:25 -0000
*************** xcoff_next_symbol_text (struct objfile *
*** 868,874 ****
    struct internal_syment symbol;
    char *retval;
    /* FIXME: is this the same as the passed arg? */
!   objfile = this_symtab_psymtab->objfile;

    bfd_coff_swap_sym_in (objfile->obfd, raw_symbol, &symbol);
    if (symbol.n_zeroes)
--- 868,875 ----
    struct internal_syment symbol;
    char *retval;
    /* FIXME: is this the same as the passed arg? */
!   if (this_symtab_psymtab)
!     objfile = this_symtab_psymtab->objfile;

    bfd_coff_swap_sym_in (objfile->obfd, raw_symbol, &symbol);
    if (symbol.n_zeroes)
*************** scan_xcoff_symtab (struct objfile *objfi
*** 2170,2175 ****
--- 2171,2177 ----
    last_source_file = NULL;

    abfd = objfile->obfd;
+   next_symbol_text_func = xcoff_next_symbol_text;

    sraw_symbol = ((struct coff_symfile_info *)
objfile->deprecated_sym_private)->symtbl;
    nsyms = ((struct coff_symfile_info *)
objfile->deprecated_sym_private)->symtbl_num_syms;


      reply	other threads:[~2006-01-02  5:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0512302200390.12982-100000@www.eyesopen.com>
2006-01-02  4:34 ` Jim Blandy
2006-01-02  5:52   ` Jim Blandy [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=8f2776cb0601012151y30cf2672i8b32f958f605a982@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=roger@eyesopen.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