🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

1 total messages Started by Simon Marshall Tue, 07 Apr 1992 13:34
temacs dies when building epoch-4.0 on a Sequent, anyone know why?
#33
Author: Simon Marshall
Date: Tue, 07 Apr 1992 13:34
84 lines
4186 bytes
	Yes, it's me again, folks.  I've joined the mailing list, but please
    also email any answers to me as there may be a lag before I'm on it...

	I managed to compile temacs (thanks to Susan Hinrichs), but ran into
    another problem.  This was with either gcc-1.40 or gcc-2.1, on a Sequent
    Symmetry S81 running DYNIX V3.0.17.10.

	When running temacs, I got some strange results.  When temacs was
    built without optimisation, I got the following:

./temacs -batch -l ../epoch-lisp/inc-vers
Please set the environment variable TERM; see tset(1).
Make[1]: *** [epoch] Error 1

	even though TERM was set.  So I ran under gdb-4.4 and found that
    SIGTRAP was being generated, apparently straight away:

GDB 4.4, Copyright 1991 Free Software Foundation, Inc...
Gdb> run -batch -l ../epoch-lisp/inc-vers
Starting program: /v4/usr/src/epoch-4.0p0/src/temacs -batch -l ../epoch-lisp/inc-vers

Program received signal 5, Trace/BPT trap
_start () at crt0.c:225
gdb> 

	Where the arrow marks the guilty point (I also notice that it
    mentions Sequent):

_start ()
=>
/* On vax, nothing is pushed here  */
/* On sequent, bogus fp is pushed here  */
  start1 ();
}

	However, when compiled with optimisation option -O, I got a
    different outcome & got a little further.  This time the problem appears
    to be by giving memcpy a NULL pointer:

GDB 4.4, Copyright 1991 Free Software Foundation, Inc...
Gdb> run -batch -l ../epoch-lisp/inc-vers
Starting program: /v4/usr/src/epoch-4.0p0/src/temacs -batch -l ../epoch-lisp/inc-vers
Loading ../epoch-lisp/inc-vers...

Program received signal 11, Segmentation fault
0x6ecbd in memcpy (0, 808660, 31)
gdb> where
#0  0x6ecbd in memcpy (0, 808660, 31)
#1  0x6d23c in _doprnt (729896, 1073736368, 752492)
#2  0x6ab82 in printf ()
#3  0x126ac in message (m=0xc56d4 "New Epoch version will be 4.0.1", 
    a1=808660, a2=2, a3=1073736424) at xdispepoch.c:438
#4  0x36128 in Fmessage (nargs=2, args=0x3fffeae8) at editfns.c:913
#5  0x390bf in Feval (form=84783172) at eval.c:1405
#6  0x3e43b in readevalloop (readcharfun=17650076, stream=0xb7b8c, 
    evalfun=0x38d4c <Feval>, printflag=0) at lread.c:408
#7  0x3e027 in Fload (str=51140012, noerror=17593356, nomessage=17593356, 
    nosuffix=17593356) at lread.c:225
#8  0x39230 in Feval (form=84757116) at eval.c:1442
#9  0x1bdc6 in top_level_2 () at keyboard.c:549
#10 0x386b1 in internal_condition_case (bfun=0x1bdb8 <top_level_2>, 
    handlers=17593616, hfun=0x1bacc <cmd_error>) at eval.c:1018
#11 0x1bdf2 in top_level_1 () at keyboard.c:557
#12 0x382c0 in internal_catch (tag=17593596, func=0x1bdc8 <top_level_1>, 
    arg=17593356) at eval.c:826
#13 0x1bd5a in command_loop () at keyboard.c:522
#14 0x1ba72 in recursive_edit_1 () at keyboard.c:408
#15 0x1ba1a in Frecursive_edit () at keyboard.c:390
#16 0x1b53c in main (argc=4, argv=0x3fffed8c, envp=0x3fffeda0) at emacs.c:575
#17 0x10bb in start1 (bogus_fp=0, argc=808526, 
    xargv=0x3fffeddc "/v4/usr/src/epoch-4.0p0/src/temacs") at crt0.c:241
gdb> 

	I am absolutely not a debugging hacker, and I have no idea what the
    problem here is.  It happens the same which ever version of gcc I use,
    so I'm not convinced that it is a compiler error, does anyone out there
    have any ideas?  Anybody managed to get epoch-4.0 up & running on a
    Sequent, and willing to lend a hand?

	Thanx in advance, Simon. 
_______________________________________________________________________________
Simon Marshall, Dept. of Computer Science, University of Hull, Hull HU6 7RX, UK
  "Football isn't about life and death.  It's more important than that." Bill
Email: S.Marshall@Hull.ac.uk    Phone: +44 482 465181    Fax: 466666   Shankley
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads