Re: Segmentation fault

Hi Mike, thanks for reporting this. Fixed in *SVN 1745*. Best Regards, Jürgen On 2/1/24 19:04, M.Hall wrote: On macos Mojave 10.15.7 x64, gnu-apl built from svn sources, apl installed into /usr/local/bin, input "[]" gives segmentation fault.  Did I build it wrong? >>>&g

Segmentation fault

On macos Mojave 10.15.7 x64, gnu-apl built from svn sources, apl installed into /usr/local/bin, input "[]" gives segmentation fault. Did I build it wrong? >>>>>> $ uname -a Darwin mbp13 19.6.0 Darwin Kernel Version 19.6.0: Tue Jun 21 21:18:39 PDT 2022; root:xnu-

Re: Segmentation fault when applying reduction over empty matrix

Hi M, thanks, fixed in SVN 1545. Best Regards, Jürgen On 3/25/22 3:12 PM, m_mis...@autistici.org wrote: Dear maintainers, Segmentation fault is encountered when I am trying to perform a

Segmentation fault when applying reduction over empty matrix

Dear maintainers, Segmentation fault is encountered when I am trying to perform a reduction over an empty matrix: +/0 0⍴1 === SEGMENTATION FAULT Here is the stack trace outputted: -- Stack trace at

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

uld be the most current source. If that's wrong, > please enlighten me. > > > -- > *From:* Blake McBride > *Sent:* Sunday, January 3, 2016 9:30 AM > *To:* Rick Mayforth > *Cc:* Juergen Sauermann; bug-apl@gnu.org > *Subject:* Re: [Bug-apl]

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

__ From: Blake McBride Sent: Sunday, January 3, 2016 9:30 AM To: Rick Mayforth Cc: Juergen Sauermann; bug-apl@gnu.org Subject: Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit On Sun, Jan 3, 2016 at 8:48 AM, Rick Mayforth mailto:gri...@msn.com>> wrote:

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

On Sun, Jan 3, 2016 at 10:42 AM, Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: > Hi, > > yes, looks like this was fixed in *SVN 10607*. > > I have the 1.6 (or should it be 2.0 ?) release of GNU APL on my TODO list, > but was too lazy to do it. > My vote is for 1.6. 2.0, for me, woul

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

Hi, yes, looks like this was fixed in SVN 10607. I have the 1.6 (or should it be 2.0 ?) release of GNU APL on my TODO list, but was too lazy to do it. Nevertheless, thank you, Rick, for reporting this. /// Jürgen

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

On Sun, Jan 3, 2016 at 8:48 AM, Rick Mayforth wrote: > ... > I got these errors running the Debian *GNU-APL* package, then did the > full compile from apl-1.5.tar.gz dated 3/29/15 from ftp.gnu.org > and ran gdb as you suggested. The following resulted > on the virtual machine

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

⌹?(Q,Q←4000)⍴10 Segmentation fault WS FULL as expected: q←4000 r←q,q s←?r⍴10 ⎕wa 291467264 ⌹s WS FULL ⌹s ^^ But then there's this: q←1500 r←?(q,q)⍴10 ⌹r Segmentation fault I got these errors running the Debian GNU-APL pa

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

commended.) >> >> Hope this helps. >> >> Blake McBride >> >> >> On Fri, Jan 1, 2016 at 2:03 PM, Rick Mayforth wrote: >> >>> The following sequence caused the fault. APL exits. The interpreter is >>> running under Debian 8 in a VMWare virtual machine with 2GB RAM & 880MB >>> swap space. One would expect a WS FULL or some other APL error in this >>> instance rather than a forced exit, no? >>> >>> >>> a←1500 1500 ⍴ ?(1500×1500)⍴10 >>> ⎕wa >>> 193433600 >>> b←⌹a >>> Segmentation fault >>> >>> >>> >>> >> >> > >

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

      b←⌹a Segmentation fault

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

with 2GB RAM & 880MB >> swap space. One would expect a WS FULL or some other APL error in this >> instance rather than a forced exit, no? >> >> >> a←1500 1500 ⍴ ?(1500×1500)⍴10 >> ⎕wa >> 193433600 >> b←⌹a >> Segmentation fault >> >> >> >> > >

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

a←1500 1500 ⍴ ?(1500×1500)⍴10       ⎕wa 193433600       b←⌹a Segmentation fault

Re: [Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

bian 8 in a VMWare virtual machine with 2GB RAM & 880MB > swap space. One would expect a WS FULL or some other APL error in this > instance rather than a forced exit, no? > > > a←1500 1500 ⍴ ?(1500×1500)⍴10 > ⎕wa > 193433600 > b←⌹a > Segmentation fault > > > >

[Bug-apl] Segmentation fault causes GNU APL version 1.5-1 AMD64 to exit

?wa 193433600 b??a Segmentation fault

Re: [Bug-apl] segmentation fault in svn 639

trace for both these functions call the same underlying function that the stack trace ends on:Value::to_varnames(std::vector >&, bool) constMy C++ is too rusty to figure this out.        ⎕nc5 5 ⍴ '3 3   '========SEGMENTATION FAULT---

Re: [Bug-apl] segmentation fault in svn 639

Hi, the stack trace (or segfault on some systems) should be fixed in SVN 640. While ISO proposes domain error, APL2 actually returns 0 instead (and so does GNU APL). I'll leave it that way. Thanks, Jürgen

Re: [Bug-apl] segmentation fault in svn 639

On Sat, Jun 20, 2015 at 12:32 PM, Louis Chretien wrote: > I agree the error message should not be as dire as a segfault, but the basic > intent seems dubious… There's nothing inherently wrong with this. Argument of ⎕EX should be a character array with rows containing identifiers (possibly padded

Re: [Bug-apl] segmentation fault in svn 639

-20, at 01:18, alexwei...@alexweiner.com > <mailto:alexwei...@alexweiner.com> wrote: > > Type this line: > ⎕ex5 5 ⍴ '3 3 ' > and then this segmentation error happens: > ====

[Bug-apl] segmentation fault in svn 639

Type this line:      ⎕ex5 5 ⍴ '3 3   'and then this segmentation error happens:====SEGMENTATION FAULT-- Stack trace at main.cc:630x7f78c4e6aead __libc_start_ma

Re: [Bug-apl] APL give a "SEGMENTATION FAULT"

[6] z←z,[1](¯1↑⍴z)↑(-w+3)↑'∇'  ⍝ add last line [7] z←z⍪' '    ⍝ and a final blank line    ∇   ∆ 'xxx'  ⍝ xxx is an unknown function name

[Bug-apl] APL give a "SEGMENTATION FAULT"

+3)↑'∇' ⍝ function definition [6] z←z,[1](¯1↑⍴z)↑(-w+3)↑'∇' ⍝ add last line [7] z←z⍪' '⍝ and a final blank line ∇ ∆ 'xxx' ⍝ xxx is an unknown function name

Re: [Bug-apl] Hi. I encountered a segmentation fault

Message - Subject: Re: [Bug-apl] Hi. I encountered a segmentation fault From: "Juergen Sauermann" Date: 4/11/15 4:13 am To: alexwei...@alexweiner.com, bug-apl@gnu.org Hi Alex, that

Re: [Bug-apl] Hi. I encountered a segmentation fault

causes a segmentation: First these are just to describe what 'in' is:       ≡in 3       ⍴⍴in 2       ⍴in 243 243 The following line causes subsequent Segmentation fault. Let me

[Bug-apl] Hi. I encountered a segmentation fault

Hi. This causes a segmentation: First these are just to describe what 'in' is: ≡in 3 ⍴⍴in 2 ⍴in 243 243 The following line causes subsequent Segmentation fault. Let me know if I need to provide more detail. out←⊃⍪/,/in LENGTH ERROR o

Re: [Bug-apl] Segmentation fault in zero take on scalar

Hi Kacpet, thanks, fixed in SVN 280. /// Jürgen On 05/21/2014 05:47 AM, Kacper Gutowski wrote: 0↑0 SEGMENTATION FAULT -- Stack trace at main.cc:122

[Bug-apl] Segmentation fault in zero take on scalar

0↑0 SEGMENTATION FAULT -- Stack trace at main.cc:122 0x7f81f5e43b45 __libc_start_main 0x4359b5 main 0x52a66d Workspace::immediate_execution(bool

Re: [Bug-apl] A segmentation fault from escape c "^c" if you are interested.

;t know if you would want this type of "Bug" report, so feel free to ignore it. ?NAME[?] [0] NAME [1] [1] sht [2] 3 [3] 45 [4] )off [5] ?MOUNT [6] ^C ==== SEGMENTATION FAULT -- Stack

[Bug-apl] A segmentation fault from escape c "^c" if you are interested.

I don't know if you would want this type of "Bug" report, so feel free to ignore it. ?NAME[?] [0] NAME [1] [1] sht [2] 3 [3] 45 [4] )off [5] ?MOUNT [6] ^C ==== SEGMENTATION FAULT --

Re: [Bug-apl] Segmentation fault with Emacs mode

Hi Blake, before the fix, )LOAD would )CLEAR first, which deletes all functions including native ones, which dlclose()s the shared library providing the native function, which invalidates all callbacks installed b the shared library. After the fix, the shared library is not dlclosed() automat

Re: [Bug-apl] Segmentation fault with Emacs mode

27; ' at Input.cc:223 > LOC: 'Input.cc:225' at Input.cc:225 > from:'1398879581362948' at Input.cc:228 > )load Devices > line:')load Devices' at Input.cc:239 > LOC: &#x

Re: [Bug-apl] Segmentation fault with Emacs mode

57' at Executable.cc:286 start: '57' at Executable.cc:328 pc_from_to.low: '57' at Executable.cc:329 pc_from_to.high: '57' at Executable.cc:330 end: '58' at Executable.cc:331 VALUE ERROR auto[11] start ^ ==

Re: [Bug-apl] Segmentation fault with Emacs mode

Hi, Hmm - below is what I get. Elias, can you reproduce the fault easily? I guess we can rule out the archive (]log 39) then. I see that there is a ⎕FX so I would do ]log 32 and ]log 33 next. /// Jürgen eedjsa@server64:~/projects/juergen/apl-1.3/src$ ./apl __ _ __ _

Re: [Bug-apl] Segmentation fault with Emacs mode

ymbol() name=⍶ read_Symbol() name=χ read_Symbol() name=λ read_Symbol() name=⍵ read_Symbol() name=⍹ read_StateIndicator() SAVED 2014-4-27 16:11:45 (GMT-5) VALUE ERROR auto[11] start ^ ======== SEGMENTATION FAULT Segmentation

Re: [Bug-apl] Segmentation fault with Emacs mode

ead_Symbol() name=⍵ read_Symbol() name=⍹ read_StateIndicator() SAVED 2014-4-27 16:11:45 (GMT-5) VALUE ERROR auto[11] start ^ ==== SEGMENTATION FAULT Process apl segmentation fault On Wed, Apr 30, 2014 at 7:56 AM, Juergen

Re: [Bug-apl] Segmentation fault with Emacs mode

^ SEGMENTATION FAULT Process apl segmentation fault On Wed, Apr 30, 2014 at 7:03 AM, Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: > Hi Blake, > > if the problem is that stderr gets lost, then it mi

Re: [Bug-apl] Segmentation fault with Emacs mode

You don't need Emacs to reproduce. All it takes is to have the backend active. You can start it my loading the library: * 'libemacs' ⎕FX 'EMACS'* and then start the server: * EMACS[1] 0* That's all it takes. After that it should be easy to reproduce the problem. Regards, Elias On 3

Re: [Bug-apl] Segmentation fault with Emacs mode

Hi, problem on my machine is that I don't have emacs installed. And without it is difficult to reproduce. Maybe Elias can help to narrow this down a little. If you are not getting a "vid=" printout then the fault is probably not where I thought it would be. The thing is that based on the info

Re: [Bug-apl] Segmentation fault with Emacs mode

Isn't this just such an example? On Wed, Apr 30, 2014 at 7:17 AM, Elias Mårtenson wrote: > The Emacs mode should not be hiding the output on standard error. If > anyone happens to see it do that, please let me know because that would > mean you've come across a bug. > > Regards, > Elias > On 30

Re: [Bug-apl] Segmentation fault with Emacs mode

The Emacs mode should not be hiding the output on standard error. If anyone happens to see it do that, please let me know because that would mean you've come across a bug. Regards, Elias On 30 Apr 2014 20:04, "Juergen Sauermann" wrote: > Hi Blake, > > if the problem is that stderr gets lost, th

Re: [Bug-apl] Segmentation fault with Emacs mode

Hi Blake, if the problem is that stderr gets lost, then it might help if you change Archive.cc line 1348: CERR << "vid=" << vid << endl; FIXME; from CERR to COUT. That should at least show the vid that tells me where in the .apl file this happens. Just a guess because i am not

Re: [Bug-apl] Segmentation fault with Emacs mode

I don't know how to get the vid printed on stderr since I only get the error running through Emacs. If someone can give me a way of simulating this error without emacs, I'd be glad to do that. Thanks. Blake On Tue, Apr 29, 2014 at 8:45 AM, Juergen Sauermann < juergen.sauerm...@t-online.de> wr

Re: [Bug-apl] Segmentation fault with Emacs mode

^ SEGMENTATION FAULT Process apl segmentation fault On Tue, Apr 29, 2014 at 8:45 AM, Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: > Hi, > > I managed to reproduce this once with )LOAD Devices (and without emacs), > but after turning Archive related > logging on an

Re: [Bug-apl] Segmentation fault with Emacs mode

Hi, I managed to reproduce this once with )LOAD Devices (and without emacs), but after turning Archive related logging on and off again I did not happen again. I have added some more printout so that I can see which value ID is causing this (SVN 237). If it happens again, please send me the .

Re: [Bug-apl] Segmentation fault with Emacs mode

t; VALUE ERROR > auto[11] start > ^ > > > ======== > SEGMENTATION FAULT > > Process apl segmentation fault > > > > On Mon, Apr 28, 2014 at 10:06 AM, Juergen Sauermann < > juergen.sauerm...@t-online.de

Re: [Bug-apl] Segmentation fault with Emacs mode

Bug is still there: EMACS_NATIVE Network listener started. Connection information: mode:tcp addr:37165 )load Devices SAVED 2014-4-27 16:11:45 (GMT-5) VALUE ERROR auto[11] start ^ SEGMENTATION FAULT Process apl

Re: [Bug-apl] Segmentation fault with Emacs mode

ote: >>>>>>>> >>>>>>>>> Greetings, >>>>>>>>> >>>>>>>>> I have a WS that has a ⎕LX to a valid function. That function, >>>>>>>>> in turn, calls another funct

Re: [Bug-apl] Segmentation fault with Emacs mode

16:11:45 (GMT-5) VALUE ERROR auto[11] start ^ ==== SEGMENTATION FAULT Process apl segmentation fault ---

Re: [Bug-apl] Segmentation fault with Emacs mode

>>> Greetings, >>>>>>>> >>>>>>>> I have a WS that has a ⎕LX to a valid function. That function, in >>>>>>>> turn, calls another function that isn't there (on purpose). >>>>>>>> &

Re: [Bug-apl] Segmentation fault with Emacs mode

>> >> Here is what I get in Emacs: >> >> EMACS_NATIVE >> Network listener started. Connection information: mode:tcp >> addr:33206 >> )load Devices >> SAVED 2014-4-27 16:1

Re: [Bug-apl] Segmentation fault with Emacs mode

d Devices > SAVED 2014-4-27 16:11:45 (GMT-5) > VALUE ERROR > auto[11] start > ^ > > > ==== > SEGMENTATION FAULT > > Process apl segmentation fault > > > > --- > > I am running the latest APL & Emacs mode code. > > Thanks. > > Blake > >

[Bug-apl] Segmentation fault with Emacs mode

33206 )load Devices SAVED 2014-4-27 16:11:45 (GMT-5) VALUE ERROR auto[11] start ^ SEGMENTATION FAULT Process apl segmentation fault ---

Re: [Bug-apl] Segmentation fault

, Blake McBride wrote: I hit some bad keys on the keyboard while attempting to get rid of a SI and ended up with a segmentation fault. Here is what happened: Note: WS test was not saved with a SI. It has a ⎕LX that causes a function named auto to execute. auto, in turn, attempted to call a

[Bug-apl] Segmentation fault

I hit some bad keys on the keyboard while attempting to get rid of a SI and ended up with a segmentation fault. Here is what happened: Note: WS test was not saved with a SI. It has a ⎕LX that causes a function named auto to execute. auto, in turn, attempted to call a function named start that

Re: [Bug-apl] segmentation fault with any use of quote-quad?

Hi Thomas, also works on my machine. Could you please send me a stack dump from gdb? /// Jürgen On 03/18/2014 03:40 PM, baruc...@gmx.com wrote: Hi, it looks like quote-quad ⍞ makes a segfault (any use seems to do it, for instance: A←⍞ ). Regards,

Re: [Bug-apl] segmentation fault with any use of quote-quad?

It works for me (and I'm sure I've used it in the past and never had a problem). Regards, Elias On 18 March 2014 22:40, wrote: > Hi, it looks like quote-quad ⍞ makes a segfault (any use seems to do it, > for instance: A←⍞ ). > > Regards, > > -- > Thomas Baruchel > >

[Bug-apl] segmentation fault with any use of quote-quad?

Hi, it looks like quote-quad ⍞ makes a segfault (any use seems to do it, for instance: A←⍞ ). Regards, -- Thomas Baruchel