🚀 go-pugleaf

In article <9322@bloom-beacon.MIT.EDU> rlcarr@athena.mit.edu (Rich Carreiro) writes:
<
<I have some questions about C startup code - what exactly does it have
<to do?  I waslooking through the KICKSTART GUIDE TO THE AMIGA and saw the
<following:
<
</* OurStart.c - simple startup code */

[Code deleted]

<I compile each with 'lc -v filename' and they compile fine.  I next do
<'blink from ourstart.o+beep.o to beep lib lib:amiga.lib' [I have
<Latice 5.02]  and it links fine.  When I run it, instant Guru 4.  When
<I recompile with debug information and do a 
<'blink from ourstart.o+beep.o to beep lib lib:amiga.lib addsym' and
<to a 'cpr beep' cpr comes up, displays the source starting at OurStart(), 
<not main(), and then locks up.  I can move slider bars and MachII keeps working
<but cpr won't respond to anything.  Note that beep.c works fine if I link
<it with c.o, lc.lib, and amiga.lib.  Also, when I link with ourstart.o, cpr
<reports that beep has 2 modules, while if I link with c.o et al., cpr says
<there is only one module.  I have looked through c.a to get an idea of what
<it is doing, but I don't know assembly.

I can see two potential problems - except I don't have manuals, so I'm
sure to make a mistake, which someone will then correct. Oh well, no
one else has poined these out, so...

1) I don't see a starting point specified for OurStart(). Maybe BLINK
defaults to someting intelligent, but I'd be leery of it.

2) In starting cpr, you should specify that it not run the startup code
(-s switch, I believe). I wouldn't be surprised if it's getting
confused and hanging.

	<mike
--
So this is where the future lies			Mike Meyer
In a beer gut belly; In an open fly			mwm@berkeley.edu
Brilcreamed, acrylic, mindless boys			ucbvax!mwm
Punching, kicking, making noise				mwm@ucbjade.BITNET