a |:@:(,@,."_ 0) b
R.E. Boss
> -Original Message-
> From: Programming On
> Behalf Of 'Bo Jacoby' via Programming
> Sent: maandag 5 maart 2018 14:35
> To: Programming Forum
> Subject: [Jprogramming] (,a,.2),.,a,.3
>
I'll have to investigate more to work out why the instability happens.
Just a note on:
> It's the pipe that's used to communicate between the processes, the
> fdopen creates buffers which do need to be independent.
The fdopen calls are used to get a FILE* for the integer file handle
which are
I tried the current j807 beta on an ubuntu machine, and did not
encounter the instability. However, since memory corruption does not
produce reliable behaviors, I'm not sure that that matters.
That said, the purpose of that fdopen is to communicate between the
two forked processes, and moving it
After some reflection: your observations about the fdopen placement
are not invalid. But it shouldn't be the case that J needs to change
here:
It's the pipe that's used to communicate between the processes, the
fdopen creates buffers which do need to be independent.
Still, if the buffers in the
Chris Double,
I recently and independently became aware of the problems with 2!:2. This
is a serious issue and we'll be working on it for this beta cycle. Any
input or suggestions your provide will be welcome.
On Wed, Mar 7, 2018 at 9:29 AM, Chris Double
wrote:
>
On Thu, Mar 8, 2018 at 3:29 AM, Chris Double wrote:
> I will investigate more though why the instability occurs.
On closer debugging, it seems to be the add2 call, not the 'fdopen'.
With no changes this errors:
2!:2 '/bin/ls'
10554 93976423924960 93976423925520
Huh...
I wonder if there's something uninitialized in libedit (or perhaps
some other supporting library) that needs to be initialized?
--
Raul
On Wed, Mar 7, 2018 at 10:26 AM, Chris Double wrote:
> On Thu, Mar 8, 2018 at 3:29 AM, Chris Double
If I comment out the call to "fa(c)" in 'jtadd2' then the segfault
goes away. Is there some memory management issue related to the
allocation and freeing of the cmd string that is going on?
On Thu, Mar 8, 2018 at 4:31 AM, Raul Miller wrote:
> Huh...
>
> I wonder if there's
I can reproduce this segmentation fault.
I have also been able to reproduce your "ill-formed number" problem. Very odd..
Thanks,
--
Raul
On Wed, Mar 7, 2018 at 9:29 AM, Chris Double wrote:
> I'll have to investigate more to work out why the instability happens.
>
I took a quick look at the 2!:2 code and it's mostly ok in that the
file descriptors returned in the array are usable. Unfortunately using
it causes spurious errors crashes:
$ jconsole
a=: (2!:2) '/bin/ls -l'
a
28836 94660922311904 94660922312464
b =: mema 1024
|ill-formed number
I assume 'fa' does some sort of recursive freeing of memory. instead
of removing the 'fa' call, Is a 'ras(c)' needed to increment some
reference count? Something like:
B jtadd2(J jt,F f1,F f2,C*cmd){A c,x;
if(f1==NULL) {jt->fopn+=2;R 1;};
On Thu, Mar 8, 2018 at 5:01 AM, Danil Osipchuk wrote:
> The issue with 2!:2 certainly is(was) not only with the memory management.
> If I remember correctly, there is a table (may be the 1!:20) which tracks
> files in use and their descriptors ( FDs or FILE*s - again not
The issue with 2!:2 certainly is(was) not only with the memory management.
If I remember correctly, there is a table (may be the 1!:20) which tracks
files in use and their descriptors ( FDs or FILE*s - again not sure now)
and the supporting 2!:2 implementation is inconsistent when filling it
On Thu, Mar 8, 2018 at 5:01 AM, Chris Double wrote:
> I assume 'fa' does some sort of recursive freeing of memory. instead
> of removing the 'fa' call, Is a 'ras(c)' needed to increment some
> reference count? Something like:
This change also fixes 1!:20:
2!:2
14 matches
Mail list logo