all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: 9927@debbugs.gnu.org
Subject: bug#9927: 24.0.90; unexec/unexmacosx fails with GCC 4.6.1 on intel Mac OS X 10.6.8
Date: Tue, 1 Nov 2011 01:24:20 +0100	[thread overview]
Message-ID: <6A5F6D17-397A-48F7-87E9-D77C09B60EC6@Freenet.DE> (raw)

Hello!

Configuration with a modified configure script (see bug#9755) and compilation are fine, until it's time to create emacs from temacs:

	--- Load Commands written to Output File ---
	Writing segment __PAGEZERO       @        0 (       0/  0x1000 @          0)
	Writing segment __TEXT           @        0 (0x1b2000/0x1b2000 @     0x1000)
	Writing segment __DATA           @ 0x1b2000 (0x1dc000/0x1dc000 @   0x1b3000)
	        section __dyld           at 0x1b2000 - 0x1b201c (sz:     0x1c)
	        section __nl_symbol_ptr  at 0x1b201c - 0x1b2b08 (sz:    0xaec)
	        section __la_symbol_ptr  at 0x1b2b08 - 0x1b36d0 (sz:    0xbc8)
	        section __const          at 0x1b36d0 - 0x1b4b08 (sz:   0x1438)
	        section __data           at 0x1b4b10 - 0x349c92 (sz: 0x195182)
	unexec: unrecognized section name in __DATA segment

Before it was reported:

	2 LC_SEGMENT            736 __DATA             0x1b3000 0x1dc000
	                           __dyld             0x1b3000     0x1c
	                           __nl_symbol_ptr    0x1b301c    0xaec
	                           __la_symbol_ptr    0x1b3b08    0xbc8
	                           __const            0x1b46d0   0x1438
	                           __data             0x1b5b10 0x195182
	                           __static_data      0x34ac92      0x3
	                           __pu_bss2          0x34ac98   0x5418
	                           __pu_bss4          0x3500b0   0x8634
	                           __bss2             0x3586e4  0x2faec
	                           __bss4             0x3881d0   0x6564

So it's presumingly the unconventional __static_data section name that produces the premature end of dumping. The GCC 4.6.1 I am using is not supported and not modified by Apple – is updating unexmacosx.c worth the effort?

--
Greetings

  Pete

Either this man is dead or my watch has stopped.
				- Groucho Marx






             reply	other threads:[~2011-11-01  0:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01  0:24 Peter Dyballa [this message]
     [not found] ` <handler.9927.B.132010738317348.ack@debbugs.gnu.org>
2012-04-17  9:17   ` bug#9927: Acknowledgement (24.0.90; unexec/unexmacosx fails with GCC 4.6.1 on intel Mac OS X 10.6.8) Peter Dyballa
2012-06-29 17:03 ` bug#9927: 24.0.90; unexec/unexmacosx fails with GCC 4.6.1 Samuel Bronson
2012-06-29 19:19   ` Peter Dyballa
2012-06-30 16:47   ` Samuel Bronson
2013-07-25 19:37     ` Glenn Morris
2014-08-09 17:05 ` bug#9927: 24.1.50; unexec/unexmacosx doesn't grok GCC 4.6+ sections Stefan Monnier
2014-08-11  1:20   ` Glenn Morris
2014-08-11  1:40   ` Samuel Bronson
2014-08-11  1:56     ` Glenn Morris
2014-09-17 18:39 ` Paul Eggert
2014-09-17 19:48   ` Glenn Morris
2014-09-17 19:59     ` Paul Eggert
2014-09-17 21:00   ` Peter Dyballa
2014-09-17 21:10     ` Paul Eggert
2014-09-18  2:37       ` Stefan Monnier
2014-09-18  5:27         ` Paul Eggert
2014-09-18 13:05           ` Stefan Monnier
2014-10-04  9:02           ` Peter Dyballa
2014-10-04 17:19             ` Paul Eggert
2014-10-04 18:18               ` Glenn Morris
2014-10-04 19:43                 ` Paul Eggert
2014-10-05 18:36               ` Peter Dyballa
2014-10-05 23:19                 ` Paul Eggert
2014-10-06  1:29                   ` Stefan Monnier
2014-10-06  2:47                     ` Paul Eggert
2014-10-06 13:15                       ` Stefan Monnier
2014-10-06 16:16           ` Peter Dyballa
2014-09-17 22:20   ` Peter Dyballa

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=6A5F6D17-397A-48F7-87E9-D77C09B60EC6@Freenet.DE \
    --to=peter_dyballa@freenet.de \
    --cc=9927@debbugs.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.