[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: executing malloced memory on ia64 or sth else? (SableVM porting)



W liście z nie, 23-02-2003, godz. 00:48, Matthew Wilcox pisze: 
> On Sat, Feb 22, 2003 at 11:41:17PM +0100, Grzegorz B. Prokopski wrote:
> > Simplyfing the whole thing - it copies some code to malloced memory
> > and then jumps to it, by executing:
> > goto *(pc->implementation);
> > where implemenation points to the code that is to be executed.
> > 
> >   (gdb) print (char*)pc->implementation
> >   $29 = 0x6000000000022800 "\v\220àK?# \001H  "
> 
> First problem -- function pointers on ia64, parisc & ppc64 are not
> pointers to the code you're going to execute, they're pointers to a
> function descriptor.
> 
> See https://lists.linuxia64.org/archives/linux-ia64/2001-March/001254.html
Ah, so that's the problem - very interesting.

I wanted to take a closer look at the assember generated by gcc for
ia64, so I added the following CFLAGS: -fverbose-asm -save-temps

It's very strange, but despite -fverbose-asm - the comments are NOT
kept along the assembler code which makes the work VERY hard.
The machine I am testing it with is woody with gcc 2.96.
Is that the problem? Or am I missing something?

Thank you for your help

					Grzegorz B. Prokopski

-- 
Grzegorz B. Prokopski <gadek@debian.org>
Debian http://www.debian.org/

Attachment: signature.asc
Description: PGP signature


Reply to: