From: Michal Ludvig <mludvig@suse.cz>
To: gdb-patches@sources.redhat.com
Subject: [RFA] dwarf2cfi.c fix for shlibs
Date: Wed, 15 May 2002 08:12:00 -0000 [thread overview]
Message-ID: <3CE27AD4.4090406@suse.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
Hi all,
this patch fixed mapping of FDE entries from shared libraries.
OK to commit to mainline and branch?
2002-05-15 Michal Ludvig <mludvig@suse.cz>
* dwarf2cfi.c (dwarf2_build_frame_info): Add objfile->section_offset
to fde->initial_location so that frames of shared libraries are mapped
correctly.
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz
[-- Attachment #2: cfi-so-simple.diff --]
[-- Type: text/plain, Size: 948 bytes --]
Index: dwarf2cfi.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2cfi.c,v
retrieving revision 1.1.2.2
diff -c -3 -p -r1.1.2.2 dwarf2cfi.c
*** dwarf2cfi.c 14 May 2002 09:50:39 -0000 1.1.2.2
--- dwarf2cfi.c 15 May 2002 15:03:06 -0000
*************** dwarf2_build_frame_info (struct objfile
*** 1476,1482 ****
fde = fde_unit_alloc ();
fde_chunks.array[fde_chunks.elems++] = fde;
! fde->initial_location = read_pointer (abfd, &start);
fde->address_range = read_pointer (abfd, &start);
for (cie = cie_chunks;
--- 1476,1483 ----
fde = fde_unit_alloc ();
fde_chunks.array[fde_chunks.elems++] = fde;
! fde->initial_location = read_pointer (abfd, &start)
! + objfile->section_offsets[objfile->sect_index_text].offsets[0];
fde->address_range = read_pointer (abfd, &start);
for (cie = cie_chunks;
next reply other threads:[~2002-05-15 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 8:12 Michal Ludvig [this message]
2002-05-20 19:05 ` Elena Zannoni
2002-05-22 6:54 ` Michal Ludvig
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=3CE27AD4.4090406@suse.cz \
--to=mludvig@suse.cz \
--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