jaledit lockup

[mattschinkel]

command line: e:\jalv2\compiler\jalv2.exe "e:\jalv2\sample
\16f877_blink.jal" -s "e:\jalv2\lib" -no-variable-reuse

I am getting a lockup with the following code (during 1 out of 2
compiles?), after running out of data space:


CONST BIT USE_LED_PIN = FALSE

;var bit led is pin_c0 -- alias
;pin_c0_direction = output
--

if USE_LED_PIN == TRUE then
forever loop
led = on
_usec_delay(1250000)
led = off
_usec_delay(250000)
end loop
end if

const word FILES_MAX = 257
const byte ENTRIES_MAX = 1
var byte*ENTRIES_MAX entry_location[FILES_MAX]

entry_location[1] = 1

[Sunish Issac]

Is it possible to send the entire code using jaledit backup command ? My gut feel is that it has nothing to do with the source, but still. What happens if you run the command from commandline ?

 

Sunish

[Matthew Schinkel]

It does not lockup in windows command prompt. I am attaching files with jaledit backup command.

Matt.

________________________________
> From: sunis...@gmail.com
> Date: Mon, 28 Sep 2009 11:07:25 +0530
> Subject: Re: jaledit lockup
> To: jal...@googlegroups.com

[vasile surducan]

Hi Sunish,

 

There is one white screen which appears randomly (once or two per day), no menu available for sending reports by emails, usually at compile time or immediately after, before programmer is starting. This happents on two different PCs.

 

Vasile

 

[Sunish Issac]

Matt,
The program compiles with the following result with jaledit.Same result except for compilation started time for 10 out of 10 tries.

Compilation started at :29-09-2009 10:49:47 AM
jal 2.4l (compiled Aug  7 2009)
0 errors, 0 warnings
[Error] (16f877_blink.jal) [Line 56]  error: Out of data space!
Compiler CommandLine:
C:\jalpack\compiler\jalv2.exe "D:\Sunish\Desktop\jaledit_lockup\jalv2\sample\16f877_blink.jal" -s "C:\jalpack\lib" -no-variable-reuse 


Not sure what's going wrong, What's the OS ? How much RAM is free ?

Sunish

On Tue, Sep 29, 2009 at 7:53 AM, Matthew Schinkel <mattsc...@hotmail.com> wrote:

It does not lockup in windows command prompt. I am attaching files with jaledit backup command.

Matt.

________________________________

> From: sunish.net@gmail.com

[Sunish Issac]

I too have got those random hangups at compile time extremely rarely, that was during testing. For past week I was out of for a retreat and couldn't check. Hopefully I'll come across it again when I actually use jaledit for coding.

pls look out ways for reproducing the bug.

Sunish

[mattschinkel]

Windows xp pro. I have 1.5gb ram in my pc. windows says 745,544k bytes
free. good pc.

I get this lockup at other random times as well with other projects I
work on.

Matt.

On Sep 29, 1:25 am, Sunish Issac <sunish....@gmail.com> wrote:
> Matt,
> The program compiles with the following result with jaledit.Same result
> except for compilation started time for 10 out of 10 tries.
>
> Compilation started at :29-09-2009 10:49:47 AM
> jal 2.4l (compiled Aug  7 2009)
> 0 errors, 0 warnings
> [Error] (16f877_blink.jal) [Line 56]  error: Out of data space!
> Compiler CommandLine:
> C:\jalpack\compiler\jalv2.exe
> "D:\Sunish\Desktop\jaledit_lockup\jalv2\sample\16f877_blink.jal" -s
> "C:\jalpack\lib" -no-variable-reuse
>
> Not sure what's going wrong, What's the OS ? How much RAM is free ?
>
> Sunish
>
> On Tue, Sep 29, 2009 at 7:53 AM, Matthew Schinkel

> <mattschin...@hotmail.com>wrote:

>
>
>
>
>
> > It does not lockup in windows command prompt. I am attaching files with
> > jaledit backup command.
>
> > Matt.
>
> > ________________________________

> > > From: sunish....@gmail.com

> > > entry_location[1] = 1- Hide quoted text -
>
> - Show quoted text -

[mattschinkel]

Is there any way I can help track down the bug?

I see you have jaledit under BSD license, can I see the source? Is
there a way I can run it from source to find the lockup?

Matt.

> > - Show quoted text -- Hide quoted text -

[vasile surducan]

How many files are you usually opening under jaledit ?

I've noticed the bug appears mostly when close a file or after compiling other file than the main jal file and try to close it. I didn't see it at compile time. 

However even the pickit2 software is hanging with the same rate...

 

Vasile

[Sunish Issac]

I have not traced where exactly the bug is, but I too started getting this lockup, so that's a good sign :-) at least I can debug.
I got the lockups (so far) only immediately after compilation and mostly when running the programmer without prompt.

Can you all please comment whether you are running a bootlaoder/programming software after compilation ?

Looks like the issue is with JVCreateProcess or ShellExecuteEx API. Also as Vasile pointed out free memory could also be a reason for the hangups.

Sunish

[Sunish Issac]

Regarding the source, its in Delphi 5 and was not properly designed. I wanted to refactor it and put it on googlecode. Usually I never get a reply from those that I gave  the source to. I can send the source, but it won't be of much help without delphi 5 and all component libraries.

Sunish

[Matthew Schinkel]

I do not use bootlaoder, and I have a seperate program for programming. I don't use the program after compile button.
 
Please send me the source if possible.
 
Thanks,
Matt.
 

---

From: sunis...@gmail.com
Date: Mon, 2 Nov 2009 11:36:33 +0530

[Sunish Issac]

When does the lockup happen for you ? Is it at time of compile ? Or at random ? Does the lockup occur while using jaledit after a machine restart or is it after a long time of usage without restart ?

Regarding the source, pls remind me in a day or two, I'm out of station.
Sunish

On Tue, Nov 3, 2009 at 5:22 AM, Matthew Schinkel <mattsc...@hotmail.com> wrote:

I do not use bootlaoder, and I have a seperate program for programming. I don't use the program after compile button.
 
Please send me the source if possible.
 
Thanks,

Matt.
 

---

From: sunish.net@gmail.com

[Matthew Schinkel]

Lockup occurs during compile. My pc has 1.5gb ram, win xp. I almost never restart my pc.
 
sometimes I compile and it locks up, then I open jaledit again and compile the same script and it doesn't lock up.
 
I think (but i'm not sure), that it only locks up on failed compiles.
 
I gave you some code that locks up on me often with jaledit, if I compile it from command line it doesn't lock up.
 
sorry I don't have much info for you
 
Matt

 

---

From: sunis...@gmail.com
Date: Tue, 3 Nov 2009 09:06:34 +0530

[mattschinkel]

Here's some code for you that locks up jaledit EVERY time. I think
it's the compiler that is locking up this time. jaledit should not
lock up if the compiler locks up, instead maybe there should be a
message in jaledit.

----------------------------------------------------------------------------------------------------------------
include 12f675 -- target PICmicro
--
-- This program assumes a 20 MHz resonator or crystal
-- is connected to pins OSC1 and OSC2.
pragma target clock 20_000_000 -- oscillator frequency
-- configuration memory settings (fuses)
pragma target OSC HS -- HS crystal or resonator
pragma target WDT disabled -- no watchdog
pragma target MCLR external -- reset externally
--
enable_digital_io() -- disable analog I/O (if any)
--

-- i2c setup
const word _i2c_bus_speed = 1 -- * 100kHz
const bit _i2c_level = true -- i2c levels (not SMB)
--
alias i2c_clock_in is pin_a0
alias i2c_clock_out is pin_a0_direction
alias i2c_data_in is pin_a1
alias i2c_data_out is pin_a1_direction
--
include i2c_software
i2c_initialize()
----------------------------------------------------------------------------------------------------------------

Matt.

[Sunish Issac]

Matt,

No luck in getting the lockup.

This is what I got when I tried compiling the code you sent

-------------------------

Compilation started at :13-11-2009 1:49:10 PM

jal 2.4l (compiled Aug  7 2009)

[Error] (lib/i2c_software.jal) [Line 31]  "i2c_scl" not defined

[Error] (lib/i2c_software.jal) [Line 32]  "i2c_sda" not defined

[Error] (lib/i2c_software.jal) [Line 33]  "i2c_scl_direction" not defined

[Error] (lib/i2c_software.jal) [Line 34]  "i2c_sda_direction" not defined

[Error] (lib/i2c_software.jal) [Line 56]  "i2c_sda_direction" not defined

[Error] (lib/i2c_software.jal) [Line 58]  "i2c_scl_direction" not defined

[Error] (lib/i2c_software.jal) [Line 83]  "i2c_sda_direction" not defined

[Error] (lib/i2c_software.jal) [Line 85]  "i2c_scl_direction" not defined

[Error] (lib/i2c_software.jal) [Line 109]  "i2c_sda_direction" not defined

[Error] (lib/i2c_software.jal) [Line 111]  "i2c_scl_direction" not defined

[Error] (lib/i2c_software.jal) [Line 113]  "i2c_scl" not defined

[Error] (lib/i2c_software.jal) [Line 113]  'loop' expected (got 'i2c_scl')

[Error] (lib/i2c_software.jal) [Line 113]  '=' expected (got '==')

[Error] (lib/i2c_software.jal) [Line 113]  'end' expected (got '==')

[Error] (lib/i2c_software.jal) [Line 113]  {WHILE starts at C:\jalpack\lib/i2c_software.jal:113}

[Error] (lib/i2c_software.jal) [Line 113]  'end' expected (got '==')

[Error] (lib/i2c_software.jal) [Line 113]  {function starts at C:\jalpack\lib/i2c_software.jal:97}

[Error] (lib/i2c_software.jal) [Line 113]  unexpected token: "=="

18 errors, 1 warnings

[Warning] (lib/i2c_software.jal) [Line 113]  boolean expression expected

Compiler CommandLine:

C:\jalpack\compiler\jalv2.exe "D:\Sunish\Desktop\ToDelete\mattkilljaledit.jal" -s "C:\jalpack\lib"  

----------------

Sunish

[mattschinkel]

yes, I know there are errors in the code. I am using jal 2.4m-beta
(compiled Aug 19 2009)

Matt.

> On Fri, Nov 13, 2009 at 1:31 PM, mattschinkel <mattschin...@hotmail.com>wrote:
>
>
>
>
>
> > Here's some code for you that locks up jaledit EVERY time. I think
> > it's the compiler that is locking up this time. jaledit should not
> > lock up if the compiler locks up, instead maybe there should be a
> > message in jaledit.
>

> > ---------------------------------------------------------------------------­-------------------------------------

> > include 12f675                    -- target PICmicro
> > --
> > -- This program assumes a 20 MHz resonator or crystal
> > -- is connected to pins OSC1 and OSC2.
> > pragma target clock 20_000_000     -- oscillator frequency
> > -- configuration memory settings (fuses)
> > pragma target OSC  HS              -- HS crystal or resonator
> > pragma target WDT  disabled        -- no watchdog
> > pragma target MCLR external        -- reset externally
> > --
> > enable_digital_io()                -- disable analog I/O (if any)
> > --
>
> > -- i2c setup
> > const word _i2c_bus_speed = 1 -- * 100kHz
> > const bit _i2c_level = true   -- i2c levels (not SMB)
> > --
> > alias i2c_clock_in   is pin_a0
> > alias i2c_clock_out  is pin_a0_direction
> > alias i2c_data_in    is pin_a1
> > alias i2c_data_out   is pin_a1_direction
> > --
> > include i2c_software
> > i2c_initialize()
>

> > ---------------------------------------------------------------------------­-------------------------------------
>
> > Matt.- Hide quoted text -