chmod g+s ineffective

On one machine I have, chmod g+s fails to set the sticky bit. The command does not return any error, but ls -l continues to show the bit not set. $ mkdir foo $ chgrp flight foo $ chmod g+ws foo $ ls -ld foo drwxrwxr-x+ 1 nort flight 0 Jun 29 06:50 foo I ran strace, and it looks

Re: chmod g+s ineffective

Greetings, Norton Allen! > On one machine I have, chmod g+s fails to set the sticky bit. The command > does not return any error, but ls -l continues to show the bit not set. > $ mkdir foo > $ chgrp flight foo > $ chmod g+ws foo > $ ls -ld foo > drwxrwxr-x+ 1 nort flight 0 Jun

Re: chmod g+s ineffective

On 6/29/2022 7:39 AM, Andrey Repin wrote: Greetings, Norton Allen! On one machine I have, chmod g+s fails to set the sticky bit. The command does not return any error, but ls -l continues to show the bit not set. $ mkdir foo $ chgrp flight foo $ chmod g+ws foo $ ls -ld foo

Re: chmod g+s ineffective

On 6/29/2022 9:18 AM, Norton Allen wrote: On 6/29/2022 7:39 AM, Andrey Repin wrote: Greetings, Norton Allen! On one machine I have, chmod g+s fails to set the sticky bit. The command does not return any error, but ls -l continues to show the bit not set. $ mkdir foo $ chgrp flight f

variables, mostly private, not included into debug symbols list on -g3 -ggdb settings

Hello list, any idea why private variables from C++ source files are not included into symbols list with -g3 and -ggdb compilation settings in gcc version 11.3.0 under Cygwin. Like that, roughly: grep isInProgress * :bool isInProgress; $nm -Cal |grep isInProgress $ So, watchpoints obviousl

Re: Cannot see plot with qt graphics_tool kit on octave-6.4.0

> - Original Message - > I cannot see a plot with qt graphics_toolkit. > > >> graphics_tookit qt; > >> plot(1:10); > > plot window is filed with black. > > I met this on two different PCs. > > On one PC, > >> plot(1:10); > Xlib: sequence lost (0x11a61 > 0x1a63) in reply type 0x0! > Xlib

Re: variables, mostly private, not included into debug symbols list on -g3 -ggdb settings

Hi Ariel, On Thu, Jun 30, 2022 at 12:38:49AM +0200, Ariel Burbaickij wrote: > Hello list, > any idea why private variables from C++ source files are not included into > symbols list with -g3 and -ggdb compilation settings in gcc version 11.3.0 > under Cygwin. Like that, roughly: > > grep isInProg

Re: variables, mostly private, not included into debug symbols list on -g3 -ggdb settings

Hello Duncan, Interesting branch to take -- I have not checked it myself but there are claims that DWARF-4 (has to be written this way too in options) is Turing-Complete -- but no, still the same in terms of information available -- which starts to look seriously strange. Kind Regards Ariel Burbai