From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Declaring external assembly procedures
Date:	5 Feb 1998 05:47:28 GMT
Organization:	The National Capital FreeNet
Lines:	20
Message-ID:	<6bbjpg$o8m@freenet-news.carleton.ca>
References:	<6bav9a$mlo AT camel18 DOT mindspring DOT com>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet3.carleton.ca
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I assume Test returns its int in eax?

Anyways it is quite likely being caused by the funky ld that comes with
RSX. Try replacing it with your normal binutils ld and see if the problem
goes away. If not, we'll have to see your assembler source.
Say you never said where the SIGSEGV happens, is it at link time, or at
runtime at the call to Test? If the latter, it might be indicative of
a problem with Test's handling of arguments (or the lack thereof) or the
stack, or of the return value. IIRC an asm routine in a DJGPP app
returning an int is expected to do so by leaving the int in eax, although
I can't see it crashing if you left garbage in eax, unless it uses eax as
a *pointer* to the return value instead or something similar.

--
    .*.  Friendship, companionship, love, and having fun are the reasons for
 -()  <  life. All else; sex, money, fame, etc.; are just to get/express these.
    `*'  Send any and all mail with attachments to the hotmail address please.
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca pgd73 AT hotmail DOT com

- Raw text -