Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: don't read coff line number unless we have symbols too
Date: Wed, 21 Aug 2002 22:52:00 -0000	[thread overview]
Message-ID: <vt2wuqj5u1h.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <npwusl99xg.fsf@zwingli.cygnus.com>


Joel Brobecker has said in private E-mail that his earlier concerns
have been addressed, so I've committed this change.

Jim Blandy <jimb@redhat.com> writes:

> "Philippe De Muyter" <phdm@macqel.be> writes:
> > Should the following lines not be kept outside of the conditional block ?
> > 
> >        info->min_lineno_offset = 0;
> >        info->max_lineno_offset = 0;
> 
> Sure, those can be moved outside.  
> 
> I was just thinking of those as just establishing the pre-condition
> for the loop that bfd_map_over_sections does.  Those fields are never
> used outside the "read the line number table" block, and the worker
> function for bfd_map_over_sections --- effectively, the loop body.  In
> that light, it makes more sense to keep them right next to the call,
> as they are in the original code.
> 
> Here's a revised patch, if you prefer the initializations outside.
> 
> 2002-03-06  Jim Blandy  <jimb@redhat.com>
> 
> 	* coffread.c (coff_symfile_read): Don't try to read the line
> 	number table from disk if the image file doesn't have a symbol
> 	table; we'll never actually look at the info anyway, and Windows
> 	ships DLL's with bogus file offsets for the line number data.
> 
> Index: gdb/coffread.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/coffread.c,v
> retrieving revision 1.26
> diff -c -r1.26 coffread.c
> *** gdb/coffread.c	19 Mar 2002 19:00:03 -0000	1.26
> --- gdb/coffread.c	26 Jun 2002 18:19:07 -0000
> ***************
> *** 593,608 ****
>   
>   /* End of warning */
>   
> -   /* Read the line number table, all at once.  */
>     info->min_lineno_offset = 0;
>     info->max_lineno_offset = 0;
> -   bfd_map_over_sections (abfd, find_linenos, (void *) info);
>   
> !   make_cleanup (free_linetab_cleanup, 0 /*ignore*/);
> !   val = init_lineno (abfd, info->min_lineno_offset,
> ! 		     info->max_lineno_offset - info->min_lineno_offset);
> !   if (val < 0)
> !     error ("\"%s\": error reading line numbers\n", name);
>   
>     /* Now read the string table, all at once.  */
>   
> --- 593,626 ----
>   
>   /* End of warning */
>   
>     info->min_lineno_offset = 0;
>     info->max_lineno_offset = 0;
>   
> !   /* Only read line number information if we have symbols.
> ! 
> !      On Windows NT, some of the system's DLL's have sections with
> !      PointerToLinenumbers fields that are non-zero, but point at
> !      random places within the image file.  (In the case I found,
> !      KERNEL32.DLL's .text section has a line number info pointer that
> !      points into the middle of the string `lib\\i386\kernel32.dll'.)
> ! 
> !      However, these DLL's also have no symbols.  The line number
> !      tables are meaningless without symbols.  And in fact, GDB never
> !      uses the line number information unless there are symbols.  So we
> !      can avoid spurious error messages (and maybe run a little
> !      faster!) by not even reading the line number table unless we have
> !      symbols.  */
> !   if (num_symbols > 0)
> !     {
> !       /* Read the line number table, all at once.  */
> !       bfd_map_over_sections (abfd, find_linenos, (void *) info);
> ! 
> !       make_cleanup (free_linetab_cleanup, 0 /*ignore*/);
> !       val = init_lineno (abfd, info->min_lineno_offset,
> !                          info->max_lineno_offset - info->min_lineno_offset);
> !       if (val < 0)
> !         error ("\"%s\": error reading line numbers\n", name);
> !     }
>   
>     /* Now read the string table, all at once.  */
>   


  reply	other threads:[~2002-08-22  5:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06 15:58 Jim Blandy
2002-06-20 11:26 ` Jim Blandy
2002-06-20 11:39   ` Daniel Jacobowitz
2002-06-20 13:47     ` Jim Blandy
2002-06-24  5:57   ` Philippe De Muyter
2002-06-24 12:10     ` Joel Brobecker
2002-06-25 15:03       ` Jim Blandy
2002-06-26  1:03         ` Philippe De Muyter
2002-06-26 11:22           ` Jim Blandy
2002-08-21 22:52             ` Jim Blandy [this message]
2002-06-24 12:32 Paul N. Hilfinger
2002-06-26 12:57 ` Jim Blandy
2002-06-24 19:30 Paul N. Hilfinger
2002-06-25 15:07 ` Jim Blandy

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=vt2wuqj5u1h.fsf@zenia.red-bean.com \
    --to=jimb@redhat.com \
    --cc=gdb-patches@sources.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