Le 21/09/2017 à 22:55, Gianluigi a écrit :
Hi Jussi,
I've run your program, I'm not getting any errors.
It create a numbered folder in /tmp/gambas.1000 with the 1.tmp file that
will be deleted at the end of the program, everything seems OK.
Tested with Gambas 3.10 on Xubuntu 16.04 and with Gambas
Hi Jussi,
I've run your program, I'm not getting any errors.
It create a numbered folder in /tmp/gambas.1000 with the 1.tmp file that
will be deleted at the end of the program, everything seems OK.
Tested with Gambas 3.10 on Xubuntu 16.04 and with Gambas 3.10.90 on Ubuntu
16.04
Note: Sometimes the
Actually, it would be equally helpful to know if there is some other system
(than Linux Mint 17.3) that can reproduce the problem... right now it's
very hard to pinpoint where the bug lives.
Jussi
On Thu, Sep 21, 2017 at 11:05 PM, Jussi Lahtinen
wrote:
> Thanks!
> Is there anyone else who use
Thanks!
Is there anyone else who use Linux Mint 17.3? If yes, can you try to run
the project couple times and report the result?
Jussi
On Thu, Sep 21, 2017 at 11:00 PM, Ingo wrote:
> Am 21.09.2017 um 21:57 schrieb Jussi Lahtinen:
>
>> Thanks! So, I'm not the only one. Can you please give me yo
Am 21.09.2017 um 21:57 schrieb Jussi Lahtinen:
Thanks! So, I'm not the only one. Can you please give me your system
information from the IDE?
Jussi
Here it is:
[System]
Gambas=3.10
OperatingSystem=Linux
Kernel=3.19.0-32-generic
Architecture=x86
Distribution=Linux Mint 17.3 Rosa
Desktop=MATE
T
Thanks! So, I'm not the only one. Can you please give me your system
information from the IDE?
Jussi
On Thu, Sep 21, 2017 at 10:53 PM, Ingo wrote:
> Am 21.09.2017 um 21:24 schrieb Jussi Lahtinen:
>
>> Can someone try to run this project (attached) to see, if I'm the only one
>> who get the deb
Am 21.09.2017 um 21:24 schrieb Jussi Lahtinen:
Can someone try to run this project (attached) to see, if I'm the only one
who get the debug messages from empty strings?
Jussi
On Tue, Sep 5, 2017 at 11:27 PM, Jussi Lahtinen
wrote:
I mean the debug information you asked
*'Uncomment the line
Can someone try to run this project (attached) to see, if I'm the only one
who get the debug messages from empty strings?
Jussi
On Tue, Sep 5, 2017 at 11:27 PM, Jussi Lahtinen
wrote:
> I mean the debug information you asked
> *'Uncomment the line #65 in the 'main/gbx/gbx_c_process.c' file
>
I mean the debug information you asked
*'Uncomment the line #65 in the 'main/gbx/gbx_c_process.c' file ("//#define
DEBUG_ME")',*
did it gave you any clue what is going on in my end?
"\r\n" is expected in the test project. That is not the problem. Here they
are attached again.
Jussi
On Tue, Sep
Le 04/09/2017 à 04:20, Jussi Lahtinen a écrit :
Benoit, any clue about this? It seems to still happen with the latest
revision.
Jussi
I saw no problem with your project. Except that printing a new line on a
terminal now sends a "\r\n" sequence by default.
--
Benoît Minisini
Benoit, any clue about this? It seems to still happen with the latest
revision.
Jussi
On Tue, Aug 22, 2017 at 12:10 AM, Jussi Lahtinen
wrote:
> OK, I made isolated loop. Here is output of the run. Just search the log
> for "Main.Main.41: sTest did not contain String 'test', instead: ''".
> Jus
OK, I made isolated loop. Here is output of the run. Just search the log
for "Main.Main.41: sTest did not contain String 'test', instead: ''".
Just in case I also attached the used project.
Jussi
On Mon, Aug 21, 2017 at 2:52 PM, Benoît Minisini <
gam...@users.sourceforge.net> wrote:
> Le 21/08/
Le 21/08/2017 à 03:34, Jussi Lahtinen a écrit :
OK, now I'm experiencing only the old already reported error, which no
one else seem to be able to reproduce. IE the variable sTest remains
empty (example in mTest.DoTest line 1686).
Jussi
Can you try that?
1) Uncomment the line #65 in the '
OK, now I'm experiencing only the old already reported error, which no one
else seem to be able to reproduce. IE the variable sTest remains empty
(example in mTest.DoTest line 1686).
Jussi
On Mon, Aug 21, 2017 at 2:47 AM, Benoît Minisini <
gam...@users.sourceforge.net> wrote:
> Le 21/08/2017 à
Le 21/08/2017 à 00:44, Jussi Lahtinen a écrit :
Hmmm... somehow this:
hWatchFile = Open "/dev/urandom" For Read Watch
Triggers execution of Process_Read(), instead of File_Read()...
something changed to that?
Jussi
No reason for that. Can you try the last commit, I added a fix.
Otherwis
Hmmm... somehow this:
hWatchFile = Open "/dev/urandom" For Read Watch
Triggers execution of Process_Read(), instead of File_Read()... something
changed to that?
Jussi
On Mon, Aug 21, 2017 at 1:38 AM, Jussi Lahtinen
wrote:
> Did you run the GambasTester? It didn't get better on my box, now it
Did you run the GambasTester? It didn't get better on my box, now it
crashes randomly in two possible ways:
mTest.Process_Read.1975: #53: Stream is closed
mTest.Process_Read.1975 mTest.DoTests.1771 mTest.Main.2212
Or:
mTest.Process_Read.1975: #42: System error #9: Bad file descriptor
mTest.Proce
Am Freitag, den 18.08.2017, 23:30 +0300 schrieb Jussi Lahtinen:
> When the fixes done in git will be available with svn?
>
>
> Jussi
>
Salut Jussi,
all I read, never, the svn is no more served, if you want the newest
Gambas Version you have to switch to git (see 'Switching to GitLab')
--
Amica
When the fixes done in git will be available with svn?
Jussi
On Fri, Aug 18, 2017 at 2:18 PM, Benoît Minisini <
gam...@users.sourceforge.net> wrote:
> Le 18/08/2017 à 12:47, Benoît Minisini via Gambas-user a écrit :
>
>> Le 14/08/2017 à 00:18, Jussi Lahtinen a écrit :
>>
>>> The freeze from gdb
SVN log doesn't say anything about the fix in r8175..?
Jussi
On Fri, Aug 18, 2017 at 8:20 PM, Benoît Minisini via Gambas-user <
gambas-user@lists.sourceforge.net> wrote:
> Le 18/08/2017 à 19:16, Karl Reinl a écrit :
>
>> Am Freitag, den 18.08.2017, 13:18 +0200 schrieb Benoît Minisini via
>> Gam
Le 18/08/2017 à 19:16, Karl Reinl a écrit :
Am Freitag, den 18.08.2017, 13:18 +0200 schrieb Benoît Minisini via
Gambas-user:
OK, fixed in commit e1a5412f4ffb5ac7af62e78c7b93e2468152b13a.
oh, thats too easy, much easier the r8175 ;°(
Indeed! Maybe a time stamp would have been clearer to comm
Am Freitag, den 18.08.2017, 13:18 +0200 schrieb Benoît Minisini via
Gambas-user:
> OK, fixed in commit e1a5412f4ffb5ac7af62e78c7b93e2468152b13a.
oh, thats too easy, much easier the r8175 ;°(
--
Amicalement
Charlie
--
C
Le 18/08/2017 à 12:47, Benoît Minisini via Gambas-user a écrit :
Le 14/08/2017 à 00:18, Jussi Lahtinen a écrit :
The freeze from gdb.
#0 0x77b068b3 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x0041e26d in WATCH_process (fd_end=fd_end@entry=4,
fd_output=-1,
timeo
Le 14/08/2017 à 00:18, Jussi Lahtinen a écrit :
The freeze from gdb.
#0 0x77b068b3 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x0041e26d in WATCH_process (fd_end=fd_end@entry=4,
fd_output=-1,
timeout=timeout@entry=0) at gbx_watch.c:685
#2 0x004286d9 in C
The freeze from gdb.
#0 0x77b068b3 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x0041e26d in WATCH_process (fd_end=fd_end@entry=4,
fd_output=-1,
timeout=timeout@entry=0) at gbx_watch.c:685
#2 0x004286d9 in CPROCESS_wait_for (process=0x688298, timeout=0)
See attached project. Module mTest.DoTests the loop starting from 1680
freezes randomly in one of the hProcess.Wait commands. This may be old bug,
because I haven't update the sources for quite a while.
[System]
Gambas=3.10.90 r8175
OperatingSystem=Linux
Kernel=3.19.0-32-generic
Architecture=x86_6
26 matches
Mail list logo
