Emacs CVS on OSX: malloc error when installing cedet

Emacs CVS on OSX: malloc error when installing cedet

[Timothee BESSET]

Hello everyone

For several days now, the CVS version of Emacs built on OSX ( 10.3 ) 
fails to install cedet  ( http://cedet.sf.net ) with the following 
error:

/Applications/Emacs.app/Contents/MacOS/Emacs -batch --no-site-file -l 
grammar-make-script -f semantic-grammar-batch-build-packages 
semantic-grammar.wy
Loading semanticdb-file (source)...
Package `semantic-grammar-wy' is up to date.
*** malloc[12002]: error for object 0x28b2169: Pointer being 
reallocated was not allocated
Fatal error (11)make[1]: *** [metagrammar] Segmentation fault
make: *** [semantic] Error 2

I can compile and install the CVS version of Emacs and cedet on a Linux 
box with no problem. This crash is happening with both the latest 
release of cedet and the CVS version. So I believe it's really an emacs 
problem, specific to the OSX port.

Also to note that I was able to run Emacs on OSX with cedet about a 
month ago. No error at the time.

Here is the configuration of my Emacs build:

Configured for `powerpc-apple-darwin7.4.0'.

   Where should the build process find the source code?    
/Users/timo/Build/emacs
   What operating system and machine description files should Emacs use?
         `s/darwin.h' and `m/powermac.h'
   What compiler should emacs be built with?               gcc 
-I/sw/include -L/sw/lib -g -O2
   Should Emacs use the GNU version of malloc?             no
     (The GNU allocators don't work with this system configuration.)
   Should Emacs use a relocating allocator for buffers?    no
   Should Emacs use mmap(2) for buffer allocation?         no
   What window system should Emacs use?                    mac
   What toolkit should Emacs use?                          none
   Where do we find X Windows header files?                NONE
   Where do we find X Windows libraries?                   NONE
   Does Emacs use -lXaw3d?                                 no
   Does Emacs use -lXpm?                                   no
   Does Emacs use -ljpeg?                                  no
   Does Emacs use -ltiff?                                  no
   Does Emacs use -lungif?                                 no
   Does Emacs use -lpng?                                   no
   Does Emacs use X toolkit scroll bars?                   no

I hope the problem can be identified and fixed soon ..

TTimo



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

Re: Emacs CVS on OSX: malloc error when installing cedet

[YAMAMOTO Mitsuharu]

>>>>> On Tue, 6 Jul 2004 12:31:14 +0200, Timothee BESSET <ttimo@idsoftware.com> said:

> I can compile and install the CVS version of Emacs and cedet on a
> Linux box with no problem. This crash is happening with both the
> latest release of cedet and the CVS version. So I believe it's
> really an emacs problem, specific to the OSX port.

It seems that the contents of `print_buffer', which is declared just
after `being_printed' in print.c, is corrupted by the following part
when print_depth == PRINT_CIRCLE.

  /* Avoid infinite recursion for circular nested structure
     in the case where Vprint_circle is nil.  */
  if (NILP (Vprint_circle))
    {
      for (i = 0; i < print_depth; i++)
	if (EQ (obj, being_printed[i]))
	  return;
      being_printed[print_depth] = obj;
    }

I tried to move the following part to just before the above one, and I
could compile CEDET 1.0beta2b.

  /* Give up if we go so deep that print_object will get an error.  */
  /* See similar code in print_object.  */
  if (print_depth >= PRINT_CIRCLE)
    return;

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp

Re: Emacs CVS on OSX: malloc error when installing cedet

[Richard Stallman]

I can't debug a problem that only occurs on MacOS,
but I do suggest that you try fetching Emacs sources as of 2 weeks
ago and see if they fail.  You could binary search in time,
and eventually narrow it down to a specific change that causes
the problem.  Then someone else might be able to intuit why.

By the way, when you're talking about a machine that runs the GNU
operating system with Linux as the kernel, could you please take an
extra second to call it a "GNU/Linux box" rather than a "Linux box"?
Thank you.

See http://www.gnu.org/gnu/gnu-linux-faq.html for more
explanation.


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com