Re: CVS emacs crashes right after startup

[Eli Zaretskii]

> From: Klaus Zeitler <address@hidden>
> Date: 08 Jan 2004 12:35:25 +0100
> 
> I figured out what had changed since my last CVS build (some time in October).
> In November they installed gcc 3.3.2 on our system, before we used gcc 3.0.4.
> When I change gcc to 3.0.4, delete temacs and run make, emacs runs fine.
> So I think it must have something to do with the final link.

Do I understand correctly that GCC 3.0.4 is used only to link `temacs',
not to compile any of the *.c source files into *.o object files?

> Size of temacs generated with 3.0.4: 12164024
> Size of temacs generated with 3.3.2:  6521914

What is the default format of debug info produced by GCC in these two
versions?  That is, if invoked with the -g switch, what debug info
format does each GCC generate?  (I'm trying to explain the almost
twofold increase in the size of the executable.)  One way of
finding out the debug info format is like this:

  gdb ./temacs
  (gdb) break main
  (gdb) run
  (gdb) info source

The last command should tell what kind of debug info is compiled into
the executable.  Please do the above both for `temacs' and for
`emacs' produced by both versions of GCC.

Also, does `temacs' work, in both cases, if invoked like this:

      temacs -q -l loadup

?  (If `temacs' works, but `emacs' does not, it's possible that the
problem happens during dumping, not during linking.)

> I never quite understood how this works with gcc and the linker. But AFAIK
> we've been using the Solaris linker with all our gcc versions.

You should be able to see which linker is invoked if you add -v to
the GCC switches in the link command line.