public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9265: exception handling faulty wenn linking PIC objects to non PIC ones Date: Tue, 04 Feb 2003 20:26:00 -0000 [thread overview] Message-ID: <20030204202601.16193.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9265; it has been noted by GNATS. From: Jakub Jelinek <jakub@redhat.com> To: Robert Schiele <rschiele@uni-mannheim.de> Cc: cc@pi3.informatik.uni-mannheim.de, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/9265: exception handling faulty wenn linking PIC objects to non PIC ones Date: Tue, 4 Feb 2003 15:19:06 -0500 On Tue, Feb 04, 2003 at 08:43:55PM +0100, Robert Schiele wrote: > On Tue, Jan 14, 2003 at 11:37:22PM +0100, Robert Schiele wrote: > > Hello Jakub. > > Hello, did you miss my last message? Could you give a comment on the > issue, or at least state that you can't/won't for any reason? > > > As you did some of the recent changes related to .eh_frame_hdr stuff > > in crtstuff, I expect you to be able to give some comments on c++/9265 > > or at least can name a person that should have an idea what the > > problem could be. Cannot reproduce this, works just fine with gcc version 3.2.1 20021207 (Red Hat Linux 8.0 3.2.1-2) GNU ld version 2.13.90.0.16 20021126 You obviously cannot mix crt* files between different gcc builds, particularly you should never use crt* files from gcc build which has #define HAVE_LD_EH_FRAME_HDR 1 in auto-host.h in gcc which does not have it. gcc which has the above defined during configure will have: %{!static:--eh-frame-hdr} in specs and thus ensure PT_GNU_EH_FRAME is created: readelf -l a.out Elf file type is EXEC (Executable file) Entry point 0x80484ac There are 7 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align PHDR 0x000034 0x08048034 0x08048034 0x000e0 0x000e0 R E 0x4 INTERP 0x000114 0x08048114 0x08048114 0x00013 0x00013 R 0x1 [Requesting program interpreter: /lib/ld-linux.so.2] LOAD 0x000000 0x08048000 0x08048000 0x00734 0x00734 R E 0x1000 LOAD 0x000734 0x08049734 0x08049734 0x00130 0x00138 RW 0x1000 DYNAMIC 0x000744 0x08049744 0x08049744 0x000e0 0x000e0 RW 0x4 NOTE 0x000128 0x08048128 0x08048128 0x00020 0x00020 R 0x4 GNU_EH_FRAME 0x000678 0x08048678 0x08048678 0x0001c 0x0001c R 0x4 Jakub
next reply other threads:[~2003-02-04 20:26 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-04 20:26 Jakub Jelinek [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-06 9:46 Robert Schiele 2003-02-04 22:40 bangerth 2003-02-04 22:36 Robert Schiele 2003-02-04 19:46 Robert Schiele 2003-01-14 22:46 Robert Schiele 2003-01-14 9:06 Robert Schiele 2003-01-14 7:06 Robert Schiele 2003-01-13 23:46 Wolfgang Bangerth 2003-01-13 23:36 Robert Schiele 2003-01-13 0:14 bangerth 2003-01-10 18:56 rschiele
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=20030204202601.16193.qmail@sources.redhat.com \ --to=jakub@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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).