[osol-discuss] iconv GB18030 problems?

2012-07-20 Thread ольга крыжановская
Can any one say why the following iconv fails in GB18030 and prints 2
'?' of the unicode character U+1F000?

printf '\xf0\x9f\x80\x80' | iconv -f 'UTF-8' -t GB18030 | iconv -f GB18030
??

My understanding is that GB18030 supports all Unicode characters with
a GBK-like encoding, right?

Olga
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| /   http://twitter.com/fleyta \ |-..-'`
  /\/\ Solaris/BSD//C/C++ programmer   /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


[osol-discuss] Creating NFSv4/ZFS XATTR through dirfd through /proc not allowed?

2012-07-13 Thread ольга крыжановская
Can some one here explain why accessing a NFSv4/ZFS xattr directory
through proc is forbidden?

To explain the problem in shell code (cd -@ is a new option to enter
the XATTR store, redirect {n}... opens a file or directory and
assigns the fd number to variable 'n'):
ksh -c 'touch x ; cd -@ x ; redirect {n}. ; cd .. ; print hello
/proc/$$/fd/$n/myxattr ; true'
/home/fleyta/bin/ksh: /proc/3982/fd/10/myxattr: cannot create
[Permission denied]

truss says the syscall fails with
open(/proc/3988/fd/10/myxattr, O_WRONLY|O_CREAT|O_TRUNC, 0666) Err#13 EACCES

Accessing files or directories through /proc/$$/fd/ from a shell
otherwise works, only the xattr directories cause trouble. Native C
code has the same problem.

Olga
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| /   http://twitter.com/fleyta \ |-..-'`
  /\/\ Solaris/BSD//C/C++ programmer   /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] [zfs-discuss] Creating NFSv4/ZFS XATTR through dirfd through /proc not allowed?

2012-07-13 Thread ольга крыжановская
Yes, accessing the files through runat works.

I think /proc (and /dev/fd, which has the same trouble but only works
if the same process accesses the fds, for obvious reasons since
/dev/fd is per process and can not be shared between processes unlike
/proc/$pid/fd/) gets confused because the directories have no name.
pfiles gets confused in a similar way and some times crashes, but
without a predictable pattern or test case.

As interestingly side note, doing a cd to the /proc/$$/fd/$fd first works:
 cut here 
touch x4 ; cd -@ x4 ; redirect {n}. ; cd .. ;
(cd /proc/$$/fd/$n ; print hello1 myxattr) ;
(cd -@ x4 ; cat myxattr ) ;
rm x4
 stop cutting here 
Accessing the file with the full path directly does not work:
 cut here 
touch x1 ; cd -@ x1 ; redirect {n}. ; cd .. ;
print hello1 /proc/$$/fd/$n/myxattr1 ;
(cd -@ x1 ; cat myxattr1 ) ;
rm x1
 stop cutting here 

Olga

On Fri, Jul 13, 2012 at 9:17 PM, Gordon Ross gordon.w.r...@gmail.com wrote:
 On Fri, Jul 13, 2012 at 2:16 AM, ольга крыжановская
 olga.kryzhanov...@gmail.com wrote:
 Can some one here explain why accessing a NFSv4/ZFS xattr directory
 through proc is forbidden?

 [...]
 truss says the syscall fails with
 open(/proc/3988/fd/10/myxattr, O_WRONLY|O_CREAT|O_TRUNC, 0666) Err#13 
 EACCES

 Accessing files or directories through /proc/$$/fd/ from a shell
 otherwise works, only the xattr directories cause trouble. Native C
 code has the same problem.

 Olga

 Does runat let you see those xattr files?

 --
 Gordon Ross g...@nexenta.com
 Nexenta Systems, Inc.  www.nexenta.com
 Enterprise class storage for everyone



-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| /   http://twitter.com/fleyta \ |-..-'`
  /\/\ Solaris/BSD//C/C++ programmer   /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] [zfs-discuss] Creating NFSv4/ZFS XATTR through dirfd through /proc not allowed?

2012-07-13 Thread ольга крыжановская
Cindy, I was not trying to open a xattr for files in /proc.
1. Please read the openat() manual page
2. I opened a fd to the directory where the xattrs are in
3. My process, for example pid 123456, now has an open fd, for example
with the number 12, which points to this xattr directory
4. Now I want to use this directory fd to create a file. If I use
openat(12, ...) the code works correct. If I use
open(/proc/123456/fd/12/myxattr,...) the code does NOT work.

IMO this is a bug in the /proc file system, because using the openat()
code path works (to prove that I am not doing some thing impossible).

Olga

On Sat, Jul 14, 2012 at 2:33 AM, Cindy Swearingen
cindy.swearin...@oracle.com wrote:
 I don't think that xattrs were ever intended or designed
 for /proc content.

 I could file an RFE for you if you wish.

 Thanks,

 Cindy


 On 07/13/12 14:00, ольга крыжановская wrote:

 Yes, accessing the files through runat works.

 I think /proc (and /dev/fd, which has the same trouble but only works
 if the same process accesses the fds, for obvious reasons since
 /dev/fd is per process and can not be shared between processes unlike
 /proc/$pid/fd/) gets confused because the directories have no name.
 pfiles gets confused in a similar way and some times crashes, but
 without a predictable pattern or test case.

 As interestingly side note, doing a cd to the /proc/$$/fd/$fd first works:
  cut here 
 touch x4 ; cd -@ x4 ; redirect {n}. ; cd .. ;
 (cd /proc/$$/fd/$n ; print hello1myxattr) ;
 (cd -@ x4 ; cat myxattr ) ;
 rm x4
  stop cutting here 
 Accessing the file with the full path directly does not work:
  cut here 
 touch x1 ; cd -@ x1 ; redirect {n}. ; cd .. ;
 print hello1/proc/$$/fd/$n/myxattr1 ;
 (cd -@ x1 ; cat myxattr1 ) ;
 rm x1
  stop cutting here 

 Olga

 On Fri, Jul 13, 2012 at 9:17 PM, Gordon Rossgordon.w.r...@gmail.com
 wrote:

 On Fri, Jul 13, 2012 at 2:16 AM, ольга крыжановская
 olga.kryzhanov...@gmail.com  wrote:

 Can some one here explain why accessing a NFSv4/ZFS xattr directory
 through proc is forbidden?

 [...]

 truss says the syscall fails with
 open(/proc/3988/fd/10/myxattr, O_WRONLY|O_CREAT|O_TRUNC, 0666) Err#13
 EACCES

 Accessing files or directories through /proc/$$/fd/ from a shell
 otherwise works, only the xattr directories cause trouble. Native C
 code has the same problem.

 Olga


 Does runat let you see those xattr files?

 --
 Gordon Rossg...@nexenta.com
 Nexenta Systems, Inc.  www.nexenta.com
 Enterprise class storage for everyone








-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| /   http://twitter.com/fleyta \ |-..-'`
  /\/\ Solaris/BSD//C/C++ programmer   /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] 32-bit noexec_user_stack on per-process basis?

2010-10-20 Thread ольга крыжановская
How does the trampoline work on architectures which have noexec bit
for stack by default, like sparcv9?

Olga

On Wed, Oct 20, 2010 at 2:26 PM,  casper@sun.com wrote:


I picture this somehow as being just a bit more functionality added to 
mprotect(2):

/* following magic to identify operating on that segment, rather than
 * a particular address
 */
#define ADDR_STACK (void *) (-1)
#define ADDR_HEAP (void *) (-2)

mprotect(ADDR_STACK, 0, (PROT_READ|PROT_WRITE|PROT_EXEC));

 It's a bit harder to bolt on the current implementation of the
 stack protection.  And what is the ADDR_STACK *all* current
 thread stacks, the stack of main or the current stack?

where a length of 0 implies something similar to what (MCL_CURRENT|MCL_FUTURE)
implies with memcntl(2), namely to apply that behavior to both the present and
future pages of the segment; that would combine applying mprotect() to the
existing pages as well as setting p_stkprot or p_datprot in the proc 
structure.

Such an interface would be ideal for runtime control either by
the developer or after-the-fact with an LD_PRELOAD'ed shared object.

Adding this functionality to mprotect() would be more understandable than
a new function, and would avoid adding an additional system call.  I don't
imagine that any existing software (except _maybe_ an emulator?) would
call mprotect() so often that the addition of a couple of if's or a switch()
applied to the addr arg would present a performance problem.

 There is one particular issue where gcc uses a trampoline created on the
 stack when you are passing a nested function as a function argument.

 (A nested function requires an additional argument)

 Casper

 ___
 opensolaris-discuss mailing list
 opensolaris-discuss@opensolaris.org




-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| /   http://twitter.com/fleyta \ |-..-'`
  /\/\ Solaris/BSD//C/C++ programmer   /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] Support options for Opensolaris?

2010-05-19 Thread ольга крыжановская
Nicholas,

I uploaded a i686 ksh93 binary tar ball for Opensolaris B134 or better
to 
http://www.nrubsig.org/people/fleyta/opensolaris/posixcore/opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz2
The binaries contain a fix which should solve your problem and a new
test suite module /usr/demo/ksh/tests/sun_solaris_math_misc.sh to
watch the bug fix.

Please install it as root by:
cd /
cp /usr/bin/ksh /usr/bin/ksh.saved
bzcat opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz2 | tar -xvof -
rm /usr/bin/ksh ; cp /usr/bin/ksh.saved /usr/bin/ksh

Hash values:
sum -x md5 opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz2
4139f70092dd40d6ee41d12cf82727dd
opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz2
sum -x sha256 opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz2
d5b1a1961644df4c217271bb89bda90f5ae02ea87be43bc9ce54fc47418d1ca6
opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz2
sum -x sha512 opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz2
b503cfc5cb6e0555c51f380d69a8cabe8db0b297c986f3171628c31c0aacd52730f3d175ac32b1e5778da474e65d5469c39a1e63cf5bc76c8b29db328668a396
opensolaris_ksh20100309_i686_20100520_rev2102.tar.bz

Let me know if the binaries do or do not fix your problem. If you need
SPARC binaries let me know.

Olga

On Wed, May 19, 2010 at 12:36 AM, Nicholas George
nicholas.george.homeoff...@googlemail.com wrote:
 Hello list,

 we wish to have the bug below handled ASAP and are looking for at
 least a year of full support for our existing Sun hardware running
 Opensolaris.
 Which support options does Oracle provide for Opensolaris?
 How can we get forward?
 How can we archive a quick solution for our existing problem?

 Nicolas

 -- Forwarded message --
 From: Nicholas George nicholas.george.homeoff...@googlemail.com
 Date: 19 May 2010 00:31
 Subject: BUG: 'integer -a z=( [1]=90 ) ; function x { nameref nz=$1 ;
 print  $((log10(nz)))==$((log10($nz))) ; } ; x z[1]' prints two
 different values
 To: ksh93-integration-disc...@opensolaris.org,
 shell-disc...@opensolaris.org, indiana-disc...@opensolaris.org


 Hello list,

 during development of an analysis/simulation software for a customer
 we ran into a nasty bug in Indiana ksh. We would appreciate any help,
 this is currently a development blocker because our software prototype
 should be implemented in a scripting language and Solaris perl lacks
 sufficient floating point resolution.

 Reproducible: Always
 Steps to Reproduce:
 Run ksh -c 'integer -a z=( [1]=90 ) ; function x { nameref nz=$1 ;
 print  $((log10(nz)))==$((log10($nz))) ; } ; x z[1]'

 Actual Results:
 The shell will print:
  -inf==1.95424250943932487459005580651023

 Expected Results:
 The shell should print identical values
  1.95424250943932487459005580651023==1.95424250943932487459005580651023

 Evaluation:
 This bug only happens if the value in the array is accessed via a
 nameref variable, the array index is greater than 0 and nz is not
 dereferenced as string like in the second call to log10().

 Nicolas
 --
 Nicholas George
 MBDA System Integration (home office)



 --
 Nicholas George
 MBDA System Integration (home office)
 ___
 opensolaris-arc mailing list
 opensolaris-...@opensolaris.org




-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| /   http://twitter.com/fleyta \ |-..-'`
  /\/\ Solaris/BSD//C/C++ programmer   /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] Q: Adding newlines to script email output

2010-05-03 Thread ольга крыжановская
Try:
= cut =
message=$( /usr/sbin/zfs list -r tank )
{
# header
printf Subject: filez ZFS Information\n\n

# message body
cat ${message}
} | mail fi...@nebol.se
= cut =

Olga

On Mon, May 3, 2010 at 8:40 PM, Ron Halstead rdhalst...@gmail.com wrote:
 Try this:

 message=`/usr/sbin/zfs list -r tank`
 echo Subject: filez ZFS Information\n\n${message}| mail filez at nebol dot 
 se

 That is curly braces around $message in the echo statement.

 ---ron
 --
 This message posted from opensolaris.org
 ___
 opensolaris-discuss mailing list
 opensolaris-discuss@opensolaris.org




-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


[osol-discuss] Garrett D'Amore still at Oracle?

2010-05-02 Thread ольга крыжановская
Is Garrett D'Amore still at Oracle? His mail post box is over flowing
and I get a DISCARD from the mail server.

Olga
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


[osol-discuss] brtfs on Solaris? (Re: [indiana-discuss] So when are we gonna fork this sucker?)

2010-04-14 Thread ольга крыжановская
brtfs could be supported on Opensolaris, too. IMO it could even
complement ZFS and spawn some concurrent development between both. ZFS
is too high end and works very poorly with less than 2GB while brtfs
reportedly works well with 128MB on ARM.

Olga

On Wed, Apr 14, 2010 at 5:31 PM,  casper@sun.com wrote:


Just a completely different question...is there any plans for btrfs ?
Will ZFS and btrfs co-exist or there's a chance that the less used one
would be dropped?

 Which OS supports both?

 Linux support brtfs, Solaris supports ZFS.

 Casper

 ___
 opensolaris-discuss mailing list
 opensolaris-discuss@opensolaris.org




-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] [website-discuss] Free OpenSolaris CD no longer offered

2010-04-14 Thread ольга крыжановская
Martin, this world becomes only bitter cold if people let it down. If
the community, Oracle included, sticks together and cooperates then
the world may become a warmer, more friendly place to all of us.

For your question about 'shipping disks for free' and a note to Derek/Valerie:
Our family get the latest Suse DVD (Tshirts and other gimmicks
included) by express mail each time a new one is released. It comes
from a Suse program to reward those who have made significant
contributions to the Suse distribution.

Derek/Valerie: Is it feasible to set up a similar program for
Opensolaris to reward those who significantly contributed to
Opensolaris?

Olga

On Wed, Apr 14, 2010 at 9:54 PM, Martin Bochnig mar...@martux.org wrote:
 On Wed, Apr 14, 2010 at 10:48 PM, Andras Barna andras.ba...@gmail.com wrote:
 https://shipit.ubuntu.com/

 Oh, thanks for the link.
 Maybe Oracle could learn from them. But I'm afraid, they could rather
 learn from Oracle!
 Because if they ship stuff around for free, work for free and want to
 benefit more people, and not just their own pockets, then they are
 doomed to end, where Sun has.

 Bitter-cold world.





 On Wed, Apr 14, 2010 at 10:41 PM, Martin Bochnig mar...@martux.org wrote:
 On Wed, Apr 14, 2010 at 10:26 PM, Chris Pickett
 pkch...@users.sourceforge.net wrote:
 On Wed, Apr 14, 2010 at 4:55 PM, Derek Cicero derek.cic...@oracle.com 
 wrote:
 FYI - Oracle is no longer offering a free OpenSolaris CD shipping program 
 at
 this time. As a result, we have removed all links and icons from the
 opensolaris.org site. If you would like to download OpenSolaris, please
 visit the Downloads page at
 http://hub.opensolaris.org/bin/view/Main/downloads.

 I saw that one coming.

 Next on this channel: Source code access on a paid subscription level
 and you have to pay $$$ per incident if you want to contribute to ON
;-(

 Chris



 Chris, which Linuex distro offers such a program, where they ship CD's
 all over the planet, FOR free [for YOU]?

 You have a link?

 If the original message would have been download section is now
 restricted access to buyers only, then I would be more on your logic.



 %martin





 --
^---^
   (@)v(@)  Chris Pickett
   |/   IT consultant
  ===m==m=== pkch...@users.sourceforge.net
 ___
 opensolaris-discuss mailing list
 opensolaris-discuss@opensolaris.org

 ___
 website-discuss mailing list
 website-disc...@opensolaris.org




 --
 http://blog.sartek.net | http://twitter.com/sartek

 ___
 opensolaris-discuss mailing list
 opensolaris-discuss@opensolaris.org




-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] ksh93 mem fault

2010-04-07 Thread ольга крыжановская
Brian, David Korn already has a fix for this. Unless this is urgent -
which I do not see right now - we go to fix this with the next resync
with the upstream sources in 2 months. We can put in a fix earlier if
it is urgent.

Olga

PS: Please move the discussion thread to
ksh93-integration-disc...@opensolaris.org

On Wed, Apr 7, 2010 at 11:49 AM, Brian Ruthven - Solaris Network
Sustaining - Oracle UK brian.ruth...@oracle.com wrote:

 A couple of points here:

 1) Is it intentional that the #! line is missing the '!' character?
 Consequently, the script will be interpreted by the current shell (which is
 presumably ksh93) rather than specifying which shell to use. Not a major
 point, but can cause confusion.
 2) /bin/ksh may not be ksh93 (it wasn't on my snv_133 system)
 3) If the #! line contains the correct path to ksh93, I do not see the
 problem.
 4) Typing the command typeset +A spaces;  spaces[0]='' directly into
 ksh93 causes the dump.

 #4 is the critical point, and to me, says this is a bug. I can't spot one
 already open, but could you visit
 http://bugs.opensolaris.org/bugdatabase/bugReport.do and log a bug please?

 Regards,
 Brian



 Robert Lawhead wrote:

 The default system shell in snv_133 segvs on code that runs correctly on
 other (earlier) versions of ksh93.

 % cat /tmp/A
 #/bin/ksh
 typeset +A spaces
 spaces[0]=''

 % echo ${.sh.version}
 Version JMP 93t+ 2009-10-12
 % /tmp/A
 Memory fault(coredump)
 % /usr/local/bin/ksh
 % echo ${.sh.version}   # works - built from AST code
 Version M 1993-12-28 s+
 % /tmp/A

 % uname -a
 SunOS ratbert2 5.11 snv_133 i86pc i386 i86pc
 % cat /etc/release
OpenSolaris Development snv_133 X86
Copyright 2010 Sun Microsystems, Inc.  All Rights Reserved.
 Use is subject to license terms.
Assembled 15 February 2010

 % ls -l /usr/bin/{,amd64}/ksh93
 -r-xr-xr-x   91 root bin  8244 Jan 22 01:02 /usr/bin//ksh93
 -r-xr-xr-x7 root bin  9848 Jan 22 01:02 /usr/bin/amd64/ksh93

 % digest -a md5 /usr/bin/{,amd64}/ksh93
 (/usr/bin//ksh93) = 596bad33627c454e2fbad70df4c29be3
 (/usr/bin/amd64/ksh93) = 9e9f9e20a9f80a1fee097a34d0b6e5da

 # dbx /usr/bin/amd64/ksh93 /var/corefiles/core.0.ksh93.16720
 Reading ksh93
 core file header read successfully
 Reading ld.so.1
 Reading libc.so.1
 Reading libshell.so.1
 Reading libcmd.so.1
 Reading libast.so.1
 Reading libm.so.2
 program terminated by signal SEGV (no mapping at the fault address)
 0xfd7fff12878b: nv_associative+0x0043:  movq
 $0x,0x0060(%r13)
 (dbx) where
 =[1] nv_associative(0x417d90, 0x417d90, 0x0, 0x0, 0xfd7fff128782, 0x0),
 at 0xfd7fff12878b
   [2] array_clone(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1269cf
   [3] clone_all_disc(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1538ec
   [4] nv_clone(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff153cf6
   [5] array_copytree(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff127045
   [6] array_grow(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff127396
   [7] nv_putsub(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x418357, 0x0, 0x0, 0x417d90,
 0x0, 0x418359, 0x8, 0x5b, 0x417d90, 0x20200, 0xfd7fffdfea30,
 0xfd7fff14c1c8, 0x1, 0x418350), at 0xfd7fff127fd7
   [8] nv_endsubscript(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1284cd
   [9] nv_create(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff14c1c8
   [10] nv_open(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff14ce2c
   [11] nv_setlist(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff14a652
   [12] sh_exec(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff171c24
   [13] exfile(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1494c6
   [14] sh_main(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff148caa
   [15] main(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x400e72



 env -i /bin/truss -eflda -rall -wall -u a.out:: -u /usr/bin/amd64/ksh93::
 /tmp/A


 Base time stamp:  1270405572.9372  [ Sun Apr  4 11:26:12 PDT 2010 ]
 16826/1: 0. execve(/usr/bin/i86/ksh93, 0x08047F60, 0x08047F6C)
 argc = 2
 16826/1: argv: sh /tmp/A
 16826/1: envp:
 16826/1: 0.0076 mmap(0x, 4096, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFB
 16826/1: 0.0078 mmap(0x, 4096, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFA
 16826/1: 0.0078 mmap(0x, 4096,
 PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF9
 16826/1: 0.0083 memcntl(0xFEFBC000, 29892, MC_ADVISE, MADV_WILLNEED,
 0, 0) = 0
 16826/1: 0.0084 memcntl(0x0805, 2536, MC_ADVISE, MADV_WILLNEED,
 0, 0) = 0
 16826/1: 0.0085 resolvepath(/usr/lib/ld.so.1, /lib/ld.so.1,
 1023) = 12
 16826/1: 0.0086 resolvepath(/usr/bin/i86/ksh93,
 /usr/bin/i86/ksh93, 1023) = 18
 16826/1: 0.0086 sysconfig(_CONFIG_PAGESIZE) =
 4096
 16826/1: 0.0087 

Re: [osol-discuss] [ksh93-integration-discuss] ksh93 mem fault

2010-04-04 Thread ольга крыжановская
Robert, what exactly do you want do do with typeset +A? To declare an
associative array you must use -A, not +A. Or did you confuse this
with set +A?

I can confirm the crash with ksh93 -c 'typeset +A spaces ;
spaces[0]=' but ksh93 -c 'typeset -A spaces ; spaces[0]=' works.

Olga

On Sun, Apr 4, 2010 at 8:32 PM, Robert Lawhead r...@ucsd.edu wrote:
 The default system shell in snv_133 segvs on code that runs correctly on
 other (earlier) versions of ksh93.

 % cat /tmp/A
 #/bin/ksh
 typeset +A spaces
 spaces[0]=''

 % echo ${.sh.version}
 Version JMP 93t+ 2009-10-12
 % /tmp/A
 Memory fault(coredump)
 % /usr/local/bin/ksh
 % echo ${.sh.version}   # works - built from AST code
 Version M 1993-12-28 s+
 % /tmp/A

 % uname -a
 SunOS ratbert2 5.11 snv_133 i86pc i386 i86pc
 % cat /etc/release
   OpenSolaris Development snv_133 X86
   Copyright 2010 Sun Microsystems, Inc.  All Rights Reserved.
Use is subject to license terms.
   Assembled 15 February 2010

 % ls -l /usr/bin/{,amd64}/ksh93
 -r-xr-xr-x   91 root bin  8244 Jan 22 01:02 /usr/bin//ksh93
 -r-xr-xr-x7 root bin  9848 Jan 22 01:02 /usr/bin/amd64/ksh93

 % digest -a md5 /usr/bin/{,amd64}/ksh93
 (/usr/bin//ksh93) = 596bad33627c454e2fbad70df4c29be3
 (/usr/bin/amd64/ksh93) = 9e9f9e20a9f80a1fee097a34d0b6e5da

 # dbx /usr/bin/amd64/ksh93 /var/corefiles/core.0.ksh93.16720
 Reading ksh93
 core file header read successfully
 Reading ld.so.1
 Reading libc.so.1
 Reading libshell.so.1
 Reading libcmd.so.1
 Reading libast.so.1
 Reading libm.so.2
 program terminated by signal SEGV (no mapping at the fault address)
 0xfd7fff12878b: nv_associative+0x0043:  movq 
 $0x,0x0060(%r13)
 (dbx) where
 =[1] nv_associative(0x417d90, 0x417d90, 0x0, 0x0, 0xfd7fff128782, 0x0), 
 at 0xfd7fff12878b
  [2] array_clone(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1269cf
  [3] clone_all_disc(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1538ec
  [4] nv_clone(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff153cf6
  [5] array_copytree(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff127045
  [6] array_grow(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff127396
  [7] nv_putsub(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x418357, 0x0, 0x0, 0x417d90, 
 0x0, 0x418359, 0x8, 0x5b, 0x417d90, 0x20200, 0xfd7fffdfea30, 
 0xfd7fff14c1c8, 0x1, 0x418350), at 0xfd7fff127fd7
  [8] nv_endsubscript(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1284cd
  [9] nv_create(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff14c1c8
  [10] nv_open(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff14ce2c
  [11] nv_setlist(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff14a652
  [12] sh_exec(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff171c24
  [13] exfile(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff1494c6
  [14] sh_main(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7fff148caa
  [15] main(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x400e72

 env -i /bin/truss -eflda -rall -wall -u a.out:: -u /usr/bin/amd64/ksh93:: 
 /tmp/A
 Base time stamp:  1270405572.9372  [ Sun Apr  4 11:26:12 PDT 2010 ]
 16826/1: 0. execve(/usr/bin/i86/ksh93, 0x08047F60, 0x08047F6C)  
 argc = 2
 16826/1: argv: sh /tmp/A
 16826/1: envp:
 16826/1: 0.0076 mmap(0x, 4096, PROT_READ|PROT_WRITE, 
 MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFB
 16826/1: 0.0078 mmap(0x, 4096, PROT_READ|PROT_WRITE, 
 MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFA
 16826/1: 0.0078 mmap(0x, 4096, 
 PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF9
 16826/1: 0.0083 memcntl(0xFEFBC000, 29892, MC_ADVISE, MADV_WILLNEED, 
 0, 0) = 0
 16826/1: 0.0084 memcntl(0x0805, 2536, MC_ADVISE, MADV_WILLNEED, 
 0, 0) = 0
 16826/1: 0.0085 resolvepath(/usr/lib/ld.so.1, /lib/ld.so.1, 1023) 
 = 12
 16826/1: 0.0086 resolvepath(/usr/bin/i86/ksh93, 
 /usr/bin/i86/ksh93, 1023) = 18
 16826/1: 0.0086 sysconfig(_CONFIG_PAGESIZE) = 4096
 16826/1: 0.0087 stat64(/usr/bin/i86/ksh93, 0x08047BE4)= 0
 16826/1: 0.0088 open(/var/ld/ld.config, O_RDONLY) Err#2 
 ENOENT
 16826/1: 0.0090 stat64(/lib/libc.so.1, 0x080473E4)= 0
 16826/1: 0.0090 resolvepath(/lib/libc.so.1, /lib/libc.so.1, 1023) 
 = 14
 16826/1: 0.0091 open(/lib/libc.so.1, O_RDONLY)= 3
 16826/1: 0.0092 mmapobj(3, MMOBJ_INTERPRET, 0xFEF90890, 0x08047450, 
 0x) = 0
 16826/1: 0.0093 close(3)= 0
 16826/1: 0.0094 memcntl(0xFEE3, 189708, MC_ADVISE, MADV_WILLNEED, 
 0, 0) = 0
 16826/1: 0.0098 mmap(0x, 4096, 
 PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEE2
 16826/1: 0.0251 mmap(0x0001, 24576, 
 PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 
 

[osol-discuss] Anyone seen Roger A. Faulkner roger.faulk...@sun.com lately?

2010-03-10 Thread ольга крыжановская
Anyone seen Roger A. Faulkner roger.faulk...@sun.com lately?

Olga
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] KSH93 problem?

2009-10-28 Thread ольга крыжановская
On 10/28/09, Kyle McDonald kmcdon...@egenera.com wrote:
 [Resend to opensolaris-discuss too.]

  Hi!

  Yesterday while debugging a shell script I think I may have found a bug
  in ksh93 from sNV b124.

Please test if the ksh93 download from
http://hub.opensolaris.org/bin/view/Project+ksh93-integration/2009-10-18
solves your problem.
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] Possible IBM aquisition of Sun

2009-03-23 Thread ольга крыжановская
On 3/23/09, Malte Hahlbeck malte+sola...@gissmo.net wrote:
 What would happen to Opensolaris and other open sourced software like 
 Glassfish, Netbeans etc.?

Solaris customers are migrated to Linux. There's no point to allow
competition to own products. IBM will be committed to existing
contracts but no new contracts will be allowed.
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


[osol-discuss] Emergency project to rescue Opensolaris from IBM (was: Re: Possible IBM aquisition of Sun)

2009-03-23 Thread ольга крыжановская
On 3/23/09, Alexander Eremin ere...@milax.org wrote:

  On Mon, 2009-03-23 at 14:51 +0100, Martin Bochnig wrote:
   2009/3/23 ольга крыжановская olga.kryzhanov...@gmail.com:
On 3/23/09, Malte Hahlbeck malte+sola...@gissmo.net wrote:
What would happen to Opensolaris and other open sourced software like 
 Glassfish, Netbeans etc.?
   
Solaris customers are migrated to Linux. There's no point to allow
competition to own products. IBM will be committed to existing
contracts but no new contracts will be allowed.
  
  
   Называешь ли ты один фантастическое будущее? Ну страшно!
  
   (Dou you call this a fantastic future? Not nice.)

  ___
   opensolaris-discuss mailing list
   opensolaris-discuss@opensolaris.org


 May be this not so terrible. I think that opensolaris community will
  survive even in an underground ;)

The community cannot survive without open code. Many parts of
Opensolaris rely on closed sources. We need an emergency project to
make as many parts of Opensolaris open source or replace them with
open source.
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Re: [osol-discuss] IBM and Auschwitz __/__ Re: Possible IBM aquisition of Sun

2009-03-23 Thread ольга крыжановская
On 3/23/09, James Carlson james.d.carl...@sun.com wrote:
 Martin Bochnig writes:
   Be also aware, that IBM supported Nazi-Germany's dead-camps, by
   selling the needed information technology to them:


 Many thanks from all of us for Godwinning this pointless thread.  It
  needed to be done.

   http://en.wikipedia.org/wiki/Godwin%27s_law

James, this is not very funny. Do you wish to hear what the Nazis did
in the Ukraine?
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] IBM and Auschwitz __/__ Re: Possible IBM aquisition of Sun

2009-03-23 Thread ольга крыжановская
On 3/23/09, Robs r...@sun.com wrote:
  At least for a couple of weeks. :)

Ah-ha.
How many weeks do we have?
-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] All builds since 104 crash my system

2009-03-22 Thread ольга крыжановская
Bad graphics card driver maybe? Which card do you use?

On 3/22/09, Mike DeMarco mikej...@yahoo.com wrote:
 Including build 110. Since build 104 I have been unable to load the OS using 
 the graphics install as it tells me no screens found. when I install in text 
 mode the system installs fine but upon reboot the system will crash with what 
 I can catch of it.
  SunOS -8000-06 type: error 1
  event type   172a7defed.

  I was able to get a crash dump of the last crash.

  Any Ideas as to what changed to start crashing my system. All builds up 
 until 105 were working fine.

  Thanks

 --
  This message posted from opensolaris.org
  ___
  opensolaris-discuss mailing list
  opensolaris-discuss@opensolaris.org



-- 
  ,   __   ,
 { \/`o;-Olga Kryzhanovska   -;o`\/ }
.'-/`-/ olga.kryzhanov...@gmail.com   \-`\-'.
 `'-..-| / Solaris/BSD//C/C++ programmer   \ |-..-'`
  /\/\ /\/\
  `--`  `--`
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org