This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: HAndling Syscalls

From: "William A. Gatliff" <bgat at billgatliff dot com>
To: savithri venkatachalapathy <venkasav at ece dot orst dot edu>
Cc: crossgcc at sources dot redhat dot com
Date: Wed, 10 Jul 2002 13:10:32 -0500
Subject: Re: HAndling Syscalls
References: <Pine.GHP.4.31.0207101011090.11777-100000@pal.ECE.ORST.EDU>
Reply-to: bgat at billgatliff dot com

Savi:


Build a "hello world" application, then use objdump to dissect it.

The best place to see how syscalls are implemented is your kernel source.


b.g.


On Wed, Jul 10, 2002 at 10:18:52AM -0700, savithri venkatachalapathy wrote:
> Hi all,
> 
> I am a newbie to compilers and linux.
> And I have some doubts about how compilers handle syscalls. It will be
> appreciated if you can throw some light on it.
> 
> I have got a crosscompiler built for AE32000. I need to figure out how
> this compiler works. How is the stack space (user, instruction,system),
> data segment, code segment allocated etc and finally how syscalls are
> handled.
> 
> Any clues or links are acknowledged.
> 
> 
> Thanks,
> savi
> 
> 
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
> 

-- 
Bill Gatliff
bgat@billgatliff.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- HAndling Syscalls
  - From: savithri venkatachalapathy

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]