From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Subject: Removing old elf/maps parsing fixes from libunwind
Date: Mon, 28 Jan 2008 11:48:00 -0000 [thread overview]
Message-ID: <1201520895.3230.27.camel@dijkstra.wildebeest.org> (raw)
Hi,
Since we aren't using these code path anymore I removed these patches
from our libunwind copy. They are not wrong though. We just don't use
them anymore and they make the diff between our version and upstream a
little messy.
frysk-imports/libunwind/ChangeLog
2007-01-25 Mark Wielaard <mwielaard@redhat.com>
Revert:
2006-09-20 Alexandre Oliva <aoliva@redhat.com>
* src/os-linux.h (maps_next): Don't error out just because
path is missing.
* include/tdep-hppa/libunwind_i.h (tdep_get_elf_image): Add as
and arg to the parameter list.
* include/tdep-ia64/libunwind_i.h (tdep_get_elf_image): Ditto.
* include/tdep-ppc64/libunwind_i.h (tdep_get_elf_image): Ditto.
* include/tdep-x86/libunwind_i.h (tdep_get_elf_image): Ditto.
* include/tdep-x86_64/libunwind_i.h (tdep_get_elf_image): Ditto.
* src/elfxx.h (get_proc_name): Ditto.
* src/elfxx.c (get_proc_name): Ditto. Adjust.
* src/hppa/Ginit.c (get_static_proc_name): Adjust.
* src/ia64/Ginit.c (get_static_proc_name): Ditto.
* src/ppc64/Ginit.c (get_static_proc_name): Ditto.
* src/x86/Ginit.c (get_static_proc_name): Ditto.
* src/x86_64/Ginit.c (get_static_proc_name): Ditto.
* src/ptrace/_UPT_find_proc_info.c (get_unwind_info): Ditto.
* src/ptrace/_UPT_get_proc_name.c (_UPT_get_proc_name): Ditto.
* src/os-hpux.c (tdep_get_elf_image): Ditto.
* src/os-linux.c (tdep_get_elf_image): Ditto. Read in 1-page
segments that start with the ELF magic.
(MAX_VDSO_SIZE): New.
2007-04-25 Nurdin Premji <npremji@redhat.com>
* src/elfxx.h (elf_map_image): map image using MAP_32BIT to
avoid address truncation issues in cross-platform unwinding.
* src/os-linux.h: (tdep_get_elf_image) Ditto for VDSO section.
* src/ptrace/_UPT_find_proc_info.c (_UPTi_find_unwind_table):
Added dummy local address space for cross-platform unwinding.
I'll post the original patches for upstream consideration.
Cheers,
Mark
reply other threads:[~2008-01-28 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1201520895.3230.27.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).