Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Oct 2007 22:59:43 +0200
From:      "Valery V.Chikalov" <valera@chikalov.dp.ua>
To:        Roman Divacky <rdivacky@freebsd.org>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: Linux emulation on FreeBSD AMD64
Message-ID:  <4724F83F.30503@chikalov.dp.ua>
In-Reply-To: <4724EA7B.3010103@chikalov.dp.ua>
References:  <4721AB07.20708@novakom.com.ua> <fg05l9$n32$2@ger.gmane.org>	<4723A8D6.6020002@chikalov.dp.ua>	<20071028112910.GA84830@freebsd.org>	<4724CBCA.30500@chikalov.dp.ua> <4724D99C.3080105@chikalov.dp.ua>	<20071028184318.GA57240@freebsd.org> <4724EA7B.3010103@chikalov.dp.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
Valery V.Chikalov wrote:
> Roman Divacky пишет:
>> On Sun, Oct 28, 2007 at 08:49:00PM +0200, Valery V.Chikalov wrote:
>>> Valery V.Chikalov wrote:
>>>> Roman Divacky wrote:
>>>>>> and got something like:
>>>>>>
>>>>>> Oct 27 19:42:59 tiger kernel: mprotect addr:2a27d000, return 0
>>>>>> Oct 27 19:42:59 tiger kernel: mprotect addr:2a7c1000, return 0
>>>>>> Oct 27 19:42:59 tiger kernel: mprotect addr:2a7cd000, return 0
>>>>>> Oct 27 19:42:59 tiger kernel: mprotect addr:2a7e2000, return 0
>>>>>> Oct 27 19:42:59 tiger kernel: mprotect addr:2a7ef000, return 0
>>>>>> Oct 27 19:43:09 tiger kernel: mprotect addr:55c00000, return 13
>>>>>> Oct 27 19:43:09 tiger kernel: mprotect addr:55c81000, return 13
>>>>>>
>>>>>> where 13 is EACCES.
>>>>> can you show what are the "prot" and "len" arguments?
>> Index: linux_machdep.c
>> ===================================================================
>> RCS file: /home/ncvs/src/sys/i386/linux/linux_machdep.c,v
>> retrieving revision 1.78
>> diff -u -r1.78 linux_machdep.c
>> --- linux_machdep.c     20 Jul 2007 08:35:18 -0000      1.78
>> +++ linux_machdep.c     28 Oct 2007 18:42:15 -0000
>> @@ -803,8 +803,10 @@
>>         bsd_args.addr = uap->addr;
>>         bsd_args.len = uap->len;
>>         bsd_args.prot = uap->prot;
>> +#if 0
>>         if (bsd_args.prot & (PROT_READ | PROT_WRITE | PROT_EXEC))
>>                 bsd_args.prot |= PROT_READ | PROT_EXEC;
>> +#endif
>>         return (mprotect(td, &bsd_args));
>>  }
>>
>>
>> does this help?
> 
> Unfortunately, no.
> 
> Just for the record: this make mprottect return success,
> but oracle coredumps nevertheless. (Sorry for rhyme :-)
> 

But despite of this is a step forward!
Oracle server itself is running!
Only sqlplus(oracle control utility) and connected client oracle process 
are coredumping. So now I can start oracle server and ever generate new 
database.

Now I am trying to understand the reasons of this coredumps. They are 
occurring rather accidental, and for example I must several times try to 
start oracle to achieve the result. Moreover after some time successful 
running and serving queries oracle server dump core and stop working too.

To make things clear: on this hardware the same oracle and FreeBSD-7.0 
(i386) are running perfectly stable. The Linux in both cases the same 
RedHat-7 (from ports of FreeBSD-5.*).

Do I need to use some "linux version" of gdb?
Gdb from the base saying me:

=====================
bash-2.04$ gdb -c oracle.core `which oracle`
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
warning: A handler for the OS ABI "GNU/Linux" is not built into this
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is this harmful? Is it possible to fix this?

configuration
of GDB.  Attempting to continue with the default i386 settings.
========================

And "bt" are not looking reasonable.

Thank you for the help.
Valery.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4724F83F.30503>