GNU bug report logs - #9927
24.1.50; unexec/unexmacosx doesn't grok GCC 4.6+ sections

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#9927: closed (24.1.50; unexec/unexmacosx doesn't grok GCC
 4.6+ sections)
Date: Thu, 18 Sep 2014 05:29:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 17 Sep 2014 22:27:56 -0700
with message-id <541A6D5C.2050903 <at> cs.ucla.edu>
and subject line Re: 24.1.50; unexec/unexmacosx doesn't grok GCC 4.6+ sections
has caused the debbugs.gnu.org bug report #9927,
regarding 24.1.50; unexec/unexmacosx doesn't grok GCC 4.6+ sections
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
9927: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9927
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>
To: bug-gnu-emacs <at> gnu.org
Subject: 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

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

[Message part 3 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Peter Dyballa <Peter_Dyballa <at> Freenet.DE>, 9927-done <at> debbugs.gnu.org
Subject: Re: 24.1.50; unexec/unexmacosx doesn't grok GCC 4.6+ sections
Date: Wed, 17 Sep 2014 22:27:56 -0700

Stefan Monnier wrote:
> Looking at the patch I have no idea how "safe" it is.

OK, thanks, I'll leave emacs-24 alone then.  Closing the bug, as it 
appears to be fixed in the trunk.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.