From: Elena Zannoni <ezannoni@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] fix for separate debug info
Date: Thu, 14 Aug 2003 20:12:00 -0000 [thread overview]
Message-ID: <16187.61195.660740.776611@localhost.redhat.com> (raw)
In-Reply-To: <16186.47455.21008.985967@localhost.redhat.com>
Elena Zannoni writes:
>
> Turns out that this patch:
> 2003-06-06 Mark Mitchell <mark@codesourcery.com>
>
> [...]
> * symfile.c [...]
> (symbol_file_add_with_addrs_or_offsets): Allocate orig_addrs
> dynamically.
> [...]
>
> broke the handling of separate debug info files.
>
> Here is a fix. Nobody had noticed this failure because you need the
> separate debug info for libraries, etc installed and because there is
> no test for this feature. I'll add one next.
>
>
> elena
>
committed to gdb-6 and mainline
elena
>
> 2003-08-13 Elena Zannoni <ezannoni@redhat.com>
>
> * symfile.c (symbol_file_add_with_addrs_or_offsets): Make sure
> orig_addrs is set up properly.
>
> Index: symfile.c
> ===================================================================
> RCS file: /cvs/uberbaum/gdb/symfile.c,v
> retrieving revision 1.101
> diff -u -p -r1.101 symfile.c
> --- symfile.c 27 Jun 2003 13:11:17 -0000 1.101
> +++ symfile.c 13 Aug 2003 22:08:27 -0000
> @@ -854,7 +854,12 @@ symbol_file_add_with_addrs_or_offsets (c
> orig_addrs = alloc_section_addr_info (bfd_count_sections (abfd));
> my_cleanups = make_cleanup (xfree, orig_addrs);
> if (addrs)
> - *orig_addrs = *addrs;
> + {
> + int i;
> + orig_addrs->num_sections = addrs->num_sections;
> + for (i = 0; i < addrs->num_sections; i++)
> + orig_addrs->other[i] = addrs->other[i];
> + }
>
> /* If the objfile uses a mapped symbol file, and we have a psymtab for
> it, then skip reading any symbols at this time. */
prev parent reply other threads:[~2003-08-14 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 22:11 Elena Zannoni
2003-08-14 20:12 ` Elena Zannoni [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=16187.61195.660740.776611@localhost.redhat.com \
--to=ezannoni@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