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

2014-05-04 Thread Juergen Sauermann
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

2014-05-03 Thread Blake McBride
Any ideas on a next step for this? Thanks! Blake On Wed, Apr 30, 2014 at 1:09 PM, Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: > Hi, > > so the last we see in Input.cc is: > > *prompt: ' ' at Input.cc:223 > > and then we call start_input(). That is a callback in

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

2014-04-30 Thread Blake McBride
Here is what I get: ]xterm off ]log 32 Log facility 'Prefix parser ' is now ON ]log 33 Log facility ' ... location information ' is now ON 'libemacs' ⎕FX 'EMACS' changed to Prefix[si=0])

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

2014-04-30 Thread Juergen Sauermann
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

2014-04-30 Thread Blake McBride
Here is what I got: ]xterm off ]log 39 Log facility ')LOAD and )SAVE details ' is now ON 'libemacs' ⎕FX 'EMACS' EMACS EMACS[1] 0 Network listener started. Connection information: mode:tcp addr:40663 )load Devices Loading file /home/blake/workspaces/Dev

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

2014-04-30 Thread Blake McBride
Got this: EMACS_NATIVE Network listener started. Connection information: mode:tcp addr:42335 ]log 39 Log facility ')LOAD and )SAVE details ' is now ON )load Devices Loading file /home/blake/workspaces/Devices.xml read_Workspace() read_Value() vid=0 read_

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

2014-04-30 Thread Blake McBride
I made the change you suggested (although the line number for me was 1378; I have the latest SVN). This is what I got: EMACS_NATIVE Network listener started. Connection information: mode:tcp addr:32954 )load Devices SAVED 2014-4-27 16:11:45 (GMT-5) VALUE ERROR auto[11] start

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

2014-04-30 Thread Elias Mårtenson
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

2014-04-30 Thread Juergen Sauermann
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

2014-04-30 Thread Blake McBride
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

2014-04-30 Thread Elias Mårtenson
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

2014-04-30 Thread Juergen Sauermann
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

2014-04-29 Thread Blake McBride
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

2014-04-29 Thread Blake McBride
Same WS, same problem. Happens every time. EMACS_NATIVE Network listener started. Connection information: mode:tcp addr:59221 )load Devices SAVED 2014-4-27 16:11:45 (GMT-5) VALUE ERROR auto[11] start ^ SEGMENTATI

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

2014-04-29 Thread Juergen Sauermann
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

2014-04-28 Thread Elias Mårtenson
Weird. I will investigate this. Regards, Elias On 28 April 2014 23:28, Blake McBride wrote: > 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[

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

2014-04-28 Thread Blake McBride
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 se

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

2014-04-28 Thread Elias Mårtenson
It's easy to reproduce even without Emacs. Just load the library and start the server prior to loading his workspace. On 28 Apr 2014 23:06, "Juergen Sauermann" wrote: > Hi, > > I have initialized current_char in SVN 234, but can't see either how this > would > make a difference. I would be inter

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

2014-04-28 Thread Juergen Sauermann
Hi, I have initialized current_char in SVN 234, but can't see either how this would make a difference. I would be interested in the workspace file as well if the error persists. /// Jürgen On 04/28/2014 06:04 AM, Elias Mårtenson wrote: I've analysed the problem using Valgrind, and it seems

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

2014-04-27 Thread Elias Mårtenson
I've analysed the problem using Valgrind, and it seems as though this is a bug in the XML_Loading_Archive class. The only reason you saw it when enabling the Emacs mode was that the native plugin caused memory layout to be slightly different. Different enough that it triggered a crash instead of ju

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

2014-04-27 Thread Elias Mårtenson
Do you have a copy of the workspace I can test with? Regards, Elias On 28 April 2014 10:48, Blake McBride wrote: > I built ans installed libemacs.so from the native directory bu same > problem. > > > > On Sun, Apr 27, 2014 at 9:42 PM, Blake McBride wrote: > >> Greetings, >> >> I have a WS that

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

2014-04-27 Thread Blake McBride
I built ans installed libemacs.so from the native directory bu same problem. On Sun, Apr 27, 2014 at 9:42 PM, Blake McBride wrote: > 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). > > > ---

[Bug-apl] Segmentation fault with Emacs mode

2014-04-27 Thread Blake McBride
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). --- Here is what I get from the terminal: )load Devices SAV