bug#366: Problem executing emacs

bug#366: Problem executing emacs

[iran]

Hi,

I'm trying to install emacs 22.1 on my workstation SUN with Solaris 10, so
when I try to execute emacs -q to test if emacs works before install it,
this message is displayed: Variable binding depth exceeds
max-specpdl-size.

Could you help me telling me how can I to resolve it and to continue with
the installation of emacs on my machine?

thanks a lot,

Iran.

bug#366: Problem executing emacs

[Stefan Monnier]

> I'm trying to install emacs 22.1 on my workstation SUN with Solaris 10, so
> when I try to execute emacs -q to test if emacs works before install it,
> this message is displayed: Variable binding depth exceeds
> max-specpdl-size.

This is odd.  Do you also get this error when you try `emacs -Q' ?
How did you compile it?  Did you get any error or suspicious warning
during compilation?


        Stefan

bug#366: Problem executing emacs

[Stefan Monnier]

> I'm trying to install emacs 22.1 on my workstation SUN with Solaris 10, so
> when I try to execute emacs -q to test if emacs works before install it,
> this message is displayed: Variable binding depth exceeds
> max-specpdl-size.

> Could you help me telling me how can I to resolve it and to continue with
> the installation of Emacs on my machine?

Do you get the same result with "emacs -Q -nw"?  How 'bout
"emacs -Q --batch" (which should just exit without doing anything)?

It is of course possible that the installation target already contains
some files and that these interact poorly, so that `make install' would
actually fix your problem.  It seems highly unlikely, tho.

If you really wan tto track down this problem, then go to ../emacs/src,
start "gdb emacs" from there, then do "b Fsignal", then "r -Q" and
whenever you get a signal do "xbacktrace" which will give you both
a C and a (crude) Lisp backtrace.  These are likely to be very long and
repetitive (and you may also hit the Fsignal breakpoint before the
actual problem, so try continuing afterwards to see if that really was
the problematic error, rather than an expected signal caught and handled
somewhere).
Then please send us the backtraces (especially the Lisp one, but the
C one as well),


        Stefan

bug#366: Problem executing emacs

[Glenn Morris]

This bug is being closed because it refers to what is now an old version
of Emacs, and because we need more information to be able to do anything
and it has not been provided. If you still see this problem with the
latest Emacs release, 23.3, please reply with the requested information
and we can reopen this report if needed.

You can view the whole report at http://debbugs.gnu.org/BUGNUMBER

Stefan Monnier wrote:

> Do you get the same result with "emacs -Q -nw"?  How 'bout
> "emacs -Q --batch" (which should just exit without doing anything)?
>
> It is of course possible that the installation target already contains
> some files and that these interact poorly, so that `make install' would
> actually fix your problem.  It seems highly unlikely, tho.
>
> If you really wan tto track down this problem, then go to ../emacs/src,
> start "gdb emacs" from there, then do "b Fsignal", then "r -Q" and
> whenever you get a signal do "xbacktrace" which will give you both
> a C and a (crude) Lisp backtrace.  These are likely to be very long and
> repetitive (and you may also hit the Fsignal breakpoint before the
> actual problem, so try continuing afterwards to see if that really was
> the problematic error, rather than an expected signal caught and handled
> somewhere).
> Then please send us the backtraces (especially the Lisp one, but the
> C one as well),