From jconnor at ...664...  Wed Dec  1 20:08:40 2010
From: jconnor at ...664... (Jason Connor)
Date: Wed, 1 Dec 2010 11:08:40 -0800
Subject: [Gambas-devel] Tiny Core Linux
Message-ID: <B1C1E55AB0574D45B5B871E9E58B6C1C01CB5AF3@...665...>

Is anyone working on a TCE for Tiny Core Linux?  It would like to be able to install Gambas applications on Tiny Core Linux.  I don't think that the IDE needs to be available, but having the runtime would be great!  Gambas allows for RAD and mix that with a 10MB linux desktop gets me thinking of many possibilities.

Thanks,
Jason




From ron at ...572...  Sun Dec  5 10:38:17 2010
From: ron at ...572... (Ron)
Date: Sun, 5 Dec 2010 10:38:17 +0100
Subject: [Gambas-devel] System error... (42)
Message-ID: <AANLkTi=K32BLTv73_x7M0DcDP=RomDBPn=66QSRcBLFC@...178...>

Ok. Sometime things get weird...

I found that my command line project wasn't running anymore...

2010/12/04 15:42:16 You have 2 new e-mails on Gmail.
2010/12/04 15:47:16 Uploaded sensor data to Bwired.
2010/12/04 15:47:21 Uploaded sensor data to Pachube.
2010/12/04 16:00:00 The Time of Day is afternoon.
2010/12/04 16:00:00 It's dark outside.
2010/12/04 16:00:00 DomotiGa is running for 0 days, 4 hrs, 12 mins, and 43 secs.
2010/12/04 16:02:21 Uploaded sensor data to Pachube.
ERROR: #42: System error. Success

System error... (42)
This error is raised when a system call returns an error that does not
match another specific Gambas error.

Hmm ok, no clue... yes it's a Linux system, although the error message
has a Windows logic in it.

Regards,
Ron_2nd.



From gambas at ...1...  Sun Dec  5 12:05:33 2010
From: gambas at ...1... (=?utf-8?q?Beno=C3=AEt_Minisini?=)
Date: Sun, 5 Dec 2010 12:05:33 +0100
Subject: [Gambas-devel] System error... (42)
In-Reply-To: <AANLkTi=K32BLTv73_x7M0DcDP=RomDBPn=66QSRcBLFC@...178...>
References: <AANLkTi=K32BLTv73_x7M0DcDP=RomDBPn=66QSRcBLFC@...178...>
Message-ID: <201012051205.33577.gambas@...1...>

> Ok. Sometime things get weird...
> 
> I found that my command line project wasn't running anymore...
> 
> 2010/12/04 15:42:16 You have 2 new e-mails on Gmail.
> 2010/12/04 15:47:16 Uploaded sensor data to Bwired.
> 2010/12/04 15:47:21 Uploaded sensor data to Pachube.
> 2010/12/04 16:00:00 The Time of Day is afternoon.
> 2010/12/04 16:00:00 It's dark outside.
> 2010/12/04 16:00:00 DomotiGa is running for 0 days, 4 hrs, 12 mins, and 43
> secs. 2010/12/04 16:02:21 Uploaded sensor data to Pachube.
> ERROR: #42: System error. Success
> 
> System error... (42)
> This error is raised when a system call returns an error that does not
> match another specific Gambas error.
> 
> Hmm ok, no clue... yes it's a Linux system, although the error message
> has a Windows logic in it.
> 
> Regards,
> Ron_2nd.
> 

Can you run your command line tool that way to know where the error comes 
from?

$ gdb gbx2
...
(gdb) break THROW
...
(gdb) run
...
... Let your program run until it stops
...
(gdb) bt
...

Then send me the result of the 'bt' gdb command.

Be sure that you have a Gambas 2 compiled with debugging symbols enabled.

And if you use Gambas 3 instead of Gambas 2, replace "gbx2" by "gbx3".

Regards,

-- 
Beno?t Minisini



From ron at ...572...  Sun Dec  5 12:11:40 2010
From: ron at ...572... (Ron)
Date: Sun, 5 Dec 2010 12:11:40 +0100
Subject: [Gambas-devel] System error... (42)
In-Reply-To: <201012051205.33577.gambas@...1...>
References: <AANLkTi=K32BLTv73_x7M0DcDP=RomDBPn=66QSRcBLFC@...178...>
	<201012051205.33577.gambas@...1...>
Message-ID: <AANLkTinZnDLDrfT8c15i63Ww2GUm16Yig+wguzQT-JCZ@...178...>

Haven't been able to reproduce it yet.
I didn't change a lot to my code, so maybe it was just a one in a
million things...
Checked my dmesg for weird system/hardware problems, but no sign off any.
Will keep you posted if it happens again...

It is on Gambas2, latest rev.

Regards,
Ron_2nd.
2010/12/5 Beno?t Minisini <gambas at ...1...>:
>> Ok. Sometime things get weird...
>>
>> I found that my command line project wasn't running anymore...
>>
>> 2010/12/04 15:42:16 You have 2 new e-mails on Gmail.
>> 2010/12/04 15:47:16 Uploaded sensor data to Bwired.
>> 2010/12/04 15:47:21 Uploaded sensor data to Pachube.
>> 2010/12/04 16:00:00 The Time of Day is afternoon.
>> 2010/12/04 16:00:00 It's dark outside.
>> 2010/12/04 16:00:00 DomotiGa is running for 0 days, 4 hrs, 12 mins, and 43
>> secs. 2010/12/04 16:02:21 Uploaded sensor data to Pachube.
>> ERROR: #42: System error. Success
>>
>> System error... (42)
>> This error is raised when a system call returns an error that does not
>> match another specific Gambas error.
>>
>> Hmm ok, no clue... yes it's a Linux system, although the error message
>> has a Windows logic in it.
>>
>> Regards,
>> Ron_2nd.
>>
>
> Can you run your command line tool that way to know where the error comes
> from?
>
> $ gdb gbx2
> ...
> (gdb) break THROW
> ...
> (gdb) run
> ...
> ... Let your program run until it stops
> ...
> (gdb) bt
> ...
>
> Then send me the result of the 'bt' gdb command.
>
> Be sure that you have a Gambas 2 compiled with debugging symbols enabled.
>
> And if you use Gambas 3 instead of Gambas 2, replace "gbx2" by "gbx3".
>
> Regards,
>
> --
> Beno?t Minisini
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Gambas-devel mailing list
> Gambas-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-devel
>



From kevinfishburne at ...590...  Sat Dec 18 03:15:07 2010
From: kevinfishburne at ...590... (Kevin Fishburne)
Date: Fri, 17 Dec 2010 21:15:07 -0500
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
Message-ID: <4D0C192B.4060602@...590...>

I've been receiving this message seemingly randomly in gb2 and now in 
gb3 using gb.image. It happens about 10% of the time upon running the 
client and seems to start around the time it begins rendering the 
graphics. The project is located here and is large due to the png 
graphics files:

http://www.eightvirtues.com/sanctimonia/software/Sanctimonia.tar.bz2

It may be a bit difficult to get it running, as it requires a client and 
server with different IP addresses so that they can communicate with 
each other. I use a VirtualBox VM in Ubuntu 10.10 with a static IP 
address to get them talking on the same PC. Please let me know if you 
need help getting the app running. You need a USB gamepad to move 
around, although this isn't necessary to raise the signal 11 as it's 
raised upon running the client.

-- 
Kevin Fishburne
Eight Virtues
www: http://sales.eightvirtues.com
e-mail: sales at ...590...
phone: (770) 853-6271




From gambas at ...1...  Sat Dec 18 15:10:37 2010
From: gambas at ...1... (=?utf-8?q?Beno=C3=AEt_Minisini?=)
Date: Sat, 18 Dec 2010 15:10:37 +0100
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <4D0C192B.4060602@...590...>
References: <4D0C192B.4060602@...590...>
Message-ID: <201012181510.37143.gambas@...1...>

> I've been receiving this message seemingly randomly in gb2 and now in
> gb3 using gb.image. It happens about 10% of the time upon running the
> client and seems to start around the time it begins rendering the
> graphics. The project is located here and is large due to the png
> graphics files:
> 
> http://www.eightvirtues.com/sanctimonia/software/Sanctimonia.tar.bz2
> 
> It may be a bit difficult to get it running, as it requires a client and
> server with different IP addresses so that they can communicate with
> each other. I use a VirtualBox VM in Ubuntu 10.10 with a static IP
> address to get them talking on the same PC. Please let me know if you
> need help getting the app running. You need a USB gamepad to move
> around, although this isn't necessary to raise the signal 11 as it's
> raised upon running the client.

You must enabled core dumps on your machine, and use gdb on it to get a 
backtrace after your program has crashed. Or use gdb directly.

Do compile gambas without optimizations before.

$ cd /xxxx/trunk
$ make clean
$ make "CFLAGS=-O0 -g" "CXXFLAGS -00 -g"
...
$ sudo make install
...
$ cd /yyyy/Sanctimonia
$ gdb gbx3
(gdb) run
...
*crash*
(gdb) bt

Then send me the result of the 'bt' command.

Regards,

-- 
Beno?t Minisini



From zachsmith022 at ...176...  Sat Dec 18 19:01:37 2010
From: zachsmith022 at ...176... (Zach Smith)
Date: Sat, 18 Dec 2010 12:01:37 -0600
Subject: [Gambas-devel] feature request: sort procedures, review source code
Message-ID: <AANLkTi=PmXC56Yxn9Kg+5nQwLqG9gsHSyLbDXty3x-hp@...178...>

How about adding the feature "Sort Procedures" and "Review Source
Code" as seen in this VB6 add-in:
	
http://www.mztools.com/v3/features.aspx

I find them useful.



From kevinfishburne at ...590...  Sat Dec 18 19:24:30 2010
From: kevinfishburne at ...590... (Kevin Fishburne)
Date: Sat, 18 Dec 2010 13:24:30 -0500
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <201012181510.37143.gambas@...1...>
References: <4D0C192B.4060602@...590...>
	<201012181510.37143.gambas@...1...>
Message-ID: <4D0CFC5E.2000802@...590...>

On 12/18/2010 09:10 AM, Beno?t Minisini wrote:
> You must enabled core dumps on your machine, and use gdb on it to get a
> backtrace after your program has crashed. Or use gdb directly.
>
> Do compile gambas without optimizations before.
>
> $ cd /xxxx/trunk
> $ make clean
> $ make "CFLAGS=-O0 -g" "CXXFLAGS -00 -g"
> ...
> $ sudo make install
> ...
> $ cd /yyyy/Sanctimonia
> $ gdb gbx3
> (gdb) run
> ...
> *crash*
> (gdb) bt
Everything went fine up until the command:

make "CFLAGS=-O0 -g" "CXXFLAGS -00 -g"

When I run that I get:

make: *** No rule to make target `CXXFLAGS -00 -g'.  Stop.

Is that what it's supposed to say?

-- 
Kevin Fishburne
Eight Virtues
www: http://sales.eightvirtues.com
e-mail: sales at ...590...
phone: (770) 853-6271




From gambas at ...1...  Sat Dec 18 19:46:25 2010
From: gambas at ...1... (=?utf-8?q?Beno=C3=AEt_Minisini?=)
Date: Sat, 18 Dec 2010 19:46:25 +0100
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <4D0CFC5E.2000802@...590...>
References: <4D0C192B.4060602@...590...>
	<201012181510.37143.gambas@...1...>
	<4D0CFC5E.2000802@...590...>
Message-ID: <201012181946.26057.gambas@...1...>

> On 12/18/2010 09:10 AM, Beno?t Minisini wrote:
> > You must enabled core dumps on your machine, and use gdb on it to get a
> > backtrace after your program has crashed. Or use gdb directly.
> > 
> > Do compile gambas without optimizations before.
> > 
> > $ cd /xxxx/trunk
> > $ make clean
> > $ make "CFLAGS=-O0 -g" "CXXFLAGS -00 -g"
> > ...
> > $ sudo make install
> > ...
> > $ cd /yyyy/Sanctimonia
> > $ gdb gbx3
> > (gdb) run
> > ...
> > *crash*
> > (gdb) bt
> 
> Everything went fine up until the command:
> 
> make "CFLAGS=-O0 -g" "CXXFLAGS -00 -g"
> 
> When I run that I get:
> 
> make: *** No rule to make target `CXXFLAGS -00 -g'.  Stop.
> 
> Is that what it's supposed to say?

I forgot an "="!

$ make "CFLAGS=-O0 -g" "CXXFLAGS=-00 -g"

-- 
Beno?t Minisini



From kevinfishburne at ...590...  Sun Dec 19 00:11:41 2010
From: kevinfishburne at ...590... (Kevin Fishburne)
Date: Sat, 18 Dec 2010 18:11:41 -0500
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <201012181946.26057.gambas@...1...>
References: <4D0C192B.4060602@...590...>	<201012181510.37143.gambas@...1...>	<4D0CFC5E.2000802@...590...>
	<201012181946.26057.gambas@...1...>
Message-ID: <4D0D3FAD.40803@...590...>

On 12/18/2010 01:46 PM, Beno?t Minisini wrote:
> I forgot an "="!
>
> $ make "CFLAGS=-O0 -g" "CXXFLAGS=-00 -g"
Thanks, that worked. I ran the app several times in gdb before it died, 
so here are the results:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4fc701d in g_type_name () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0  0x00007ffff4fc701d in g_type_name () from /usr/lib/libgobject-2.0.so.0
#1  0x00007ffff6847ba5 in gtk_rc_get_style_by_paths () from 
/usr/lib/libgtk-x11-2.0.so.0
#2  0x00007ffff6d258e4 in gt_get_style (name=0x7ffff6d63cb0 "GtkEntry", 
type=0) at gtools.cpp:1116
#3  0x00007ffff6d2c561 in gDesktop::fgColor () at gdesktop.cpp:180
#4  0x00007ffff6d2c219 in gDraw::connect (this=0x7fffe01e5e80, 
wid=0x7fffe0197e10) at gdraw.cpp:176
#5  0x00007ffff6d49ea8 in begin (d=0x7fffe0230138) at CDraw.cpp:60
#6  0x00007ffff05d3721 in DRAW_begin (device=0x7fffe0197d68) at CDraw.c:91
#7  0x00007ffff05d37d5 in CDRAW_begin (_object=0x0, _param=0x683f28) at 
CDraw.c:110
#8  0x0000000000410f9c in EXEC_native () at gbx_exec.c:1243
#9  0x000000000040feac in EXEC_native_check (defined=1 '\001') at 
gbx_exec.c:1035
#10 0x0000000000452eb8 in EXEC_loop () at gbx_exec_loop.c:970
#11 0x000000000040f51a in EXEC_function_loop () at gbx_exec.c:861
#12 0x000000000040f47d in EXEC_function_real () at gbx_exec.c:848
#13 0x0000000000411ddf in EXEC_public_desc (class=0x7fffe0008b68, 
object=0x7fffe009a0e8, desc=0x7fffe0097f68, nparam=0) at gbx_exec.c:1497
#14 0x0000000000431236 in raise_event (observer=0x7fffe009a0e8, 
object=0x7fffe00dced8, func_id=163, nparam=0) at gbx_api.c:473
#15 0x000000000043165a in GB_Raise (object=0x7fffe00dced8, event_id=16, 
nparam=0) at gbx_api.c:573
#16 0x00007ffff6d502b5 in gb_raise_button_Click (sender=<value optimized 
out>) at CButton.cpp:38
#17 0x00007ffff4faca6e in g_closure_invoke () from 
/usr/lib/libgobject-2.0.so.0
#18 0x00007ffff4fc24d7 in ?? () from /usr/lib/libgobject-2.0.so.0
#19 0x00007ffff4fc3996 in g_signal_emit_valist () from 
/usr/lib/libgobject-2.0.so.0
#20 0x00007ffff4fc3f53 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#21 0x00007ffff6754e85 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#22 0x00007ffff4faca6e in g_closure_invoke () from 
/usr/lib/libgobject-2.0.so.0
#23 0x00007ffff4fc1da1 in ?? () from /usr/lib/libgobject-2.0.so.0
#24 0x00007ffff4fc3996 in g_signal_emit_valist () from 
/usr/lib/libgobject-2.0.so.0
#25 0x00007ffff4fc3f53 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#26 0x00007ffff6753b8d in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#27 0x00007ffff68019d8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#28 0x00007ffff4faca6e in g_closure_invoke () from 
/usr/lib/libgobject-2.0.so.0
#29 0x00007ffff4fc2120 in ?? () from /usr/lib/libgobject-2.0.so.0
#30 0x00007ffff4fc37db in g_signal_emit_valist () from 
/usr/lib/libgobject-2.0.so.0
#31 0x00007ffff4fc3f53 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#32 0x00007ffff691a6df in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#33 0x00007ffff67f9e73 in gtk_propagate_event () from 
/usr/lib/libgtk-x11-2.0.so.0
#34 0x00007ffff67faf4b in gtk_main_do_event () from 
/usr/lib/libgtk-x11-2.0.so.0
#35 0x00007ffff6d5dba4 in gambas_handle_event (event=0x7fffe0183110) at 
gapplication.cpp:584
#36 0x00007ffff647474c in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#37 0x00007ffff44c4342 in g_main_context_dispatch () from 
/lib/libglib-2.0.so.0
#38 0x00007ffff44c82a8 in ?? () from /lib/libglib-2.0.so.0
#39 0x00007ffff44c845c in g_main_context_iteration () from 
/lib/libglib-2.0.so.0
#40 0x00007ffff67fb22d in gtk_main_iteration_do () from 
/usr/lib/libgtk-x11-2.0.so.0
#41 0x00007ffff6d5ba57 in do_iteration (do_not_block=<value optimized 
out>, do_not_sleep=false) at main.cpp:502
#42 0x00007ffff6d5be96 in my_loop () at main.cpp:430
#43 0x000000000043d400 in main (argc=1, argv=0x7fffffffe2f8) at gbx.c:371

Doesn't make any sense to me, but hopefully it will to you. I removed my 
project that I linked to earlier, so let me know if you still need it.

-- 
Kevin Fishburne
Eight Virtues
www: http://sales.eightvirtues.com
e-mail: sales at ...590...
phone: (770) 853-6271




From gambas at ...1...  Sun Dec 19 03:57:56 2010
From: gambas at ...1... (=?utf-8?q?Beno=C3=AEt_Minisini?=)
Date: Sun, 19 Dec 2010 03:57:56 +0100
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <4D0D3FAD.40803@...590...>
References: <4D0C192B.4060602@...590...>
	<201012181946.26057.gambas@...1...>
	<4D0D3FAD.40803@...590...>
Message-ID: <201012190357.57038.gambas@...1...>

> On 12/18/2010 01:46 PM, Beno?t Minisini wrote:
> > I forgot an "="!
> > 
> > $ make "CFLAGS=-O0 -g" "CXXFLAGS=-00 -g"
> 
> Thanks, that worked. I ran the app several times in gdb before it died,
> so here are the results:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff4fc701d in g_type_name () from /usr/lib/libgobject-2.0.so.0
> (gdb) bt
> #0  0x00007ffff4fc701d in g_type_name () from /usr/lib/libgobject-2.0.so.0
> #1  0x00007ffff6847ba5 in gtk_rc_get_style_by_paths () from
> /usr/lib/libgtk-x11-2.0.so.0
> #2  0x00007ffff6d258e4 in gt_get_style (name=0x7ffff6d63cb0 "GtkEntry",
> type=0) at gtools.cpp:1116
> #3  0x00007ffff6d2c561 in gDesktop::fgColor () at gdesktop.cpp:180
> #4  0x00007ffff6d2c219 in gDraw::connect (this=0x7fffe01e5e80,
> wid=0x7fffe0197e10) at gdraw.cpp:176
> #5  0x00007ffff6d49ea8 in begin (d=0x7fffe0230138) at CDraw.cpp:60
> #6  0x00007ffff05d3721 in DRAW_begin (device=0x7fffe0197d68) at CDraw.c:91
> #7  0x00007ffff05d37d5 in CDRAW_begin (_object=0x0, _param=0x683f28) at
> CDraw.c:110
> #8  0x0000000000410f9c in EXEC_native () at gbx_exec.c:1243
> #9  0x000000000040feac in EXEC_native_check (defined=1 '\001') at
> gbx_exec.c:1035
> #10 0x0000000000452eb8 in EXEC_loop () at gbx_exec_loop.c:970
> #11 0x000000000040f51a in EXEC_function_loop () at gbx_exec.c:861
> #12 0x000000000040f47d in EXEC_function_real () at gbx_exec.c:848
> #13 0x0000000000411ddf in EXEC_public_desc (class=0x7fffe0008b68,
> object=0x7fffe009a0e8, desc=0x7fffe0097f68, nparam=0) at gbx_exec.c:1497
> #14 0x0000000000431236 in raise_event (observer=0x7fffe009a0e8,
> object=0x7fffe00dced8, func_id=163, nparam=0) at gbx_api.c:473
> #15 0x000000000043165a in GB_Raise (object=0x7fffe00dced8, event_id=16,
> nparam=0) at gbx_api.c:573
> #16 0x00007ffff6d502b5 in gb_raise_button_Click (sender=<value optimized
> out>) at CButton.cpp:38
> #17 0x00007ffff4faca6e in g_closure_invoke () from
> /usr/lib/libgobject-2.0.so.0
> #18 0x00007ffff4fc24d7 in ?? () from /usr/lib/libgobject-2.0.so.0
> #19 0x00007ffff4fc3996 in g_signal_emit_valist () from
> /usr/lib/libgobject-2.0.so.0
> #20 0x00007ffff4fc3f53 in g_signal_emit () from
> /usr/lib/libgobject-2.0.so.0 #21 0x00007ffff6754e85 in ?? () from
> /usr/lib/libgtk-x11-2.0.so.0
> #22 0x00007ffff4faca6e in g_closure_invoke () from
> /usr/lib/libgobject-2.0.so.0
> #23 0x00007ffff4fc1da1 in ?? () from /usr/lib/libgobject-2.0.so.0
> #24 0x00007ffff4fc3996 in g_signal_emit_valist () from
> /usr/lib/libgobject-2.0.so.0
> #25 0x00007ffff4fc3f53 in g_signal_emit () from
> /usr/lib/libgobject-2.0.so.0 #26 0x00007ffff6753b8d in ?? () from
> /usr/lib/libgtk-x11-2.0.so.0
> #27 0x00007ffff68019d8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
> #28 0x00007ffff4faca6e in g_closure_invoke () from
> /usr/lib/libgobject-2.0.so.0
> #29 0x00007ffff4fc2120 in ?? () from /usr/lib/libgobject-2.0.so.0
> #30 0x00007ffff4fc37db in g_signal_emit_valist () from
> /usr/lib/libgobject-2.0.so.0
> #31 0x00007ffff4fc3f53 in g_signal_emit () from
> /usr/lib/libgobject-2.0.so.0 #32 0x00007ffff691a6df in ?? () from
> /usr/lib/libgtk-x11-2.0.so.0
> #33 0x00007ffff67f9e73 in gtk_propagate_event () from
> /usr/lib/libgtk-x11-2.0.so.0
> #34 0x00007ffff67faf4b in gtk_main_do_event () from
> /usr/lib/libgtk-x11-2.0.so.0
> #35 0x00007ffff6d5dba4 in gambas_handle_event (event=0x7fffe0183110) at
> gapplication.cpp:584
> #36 0x00007ffff647474c in ?? () from /usr/lib/libgdk-x11-2.0.so.0
> #37 0x00007ffff44c4342 in g_main_context_dispatch () from
> /lib/libglib-2.0.so.0
> #38 0x00007ffff44c82a8 in ?? () from /lib/libglib-2.0.so.0
> #39 0x00007ffff44c845c in g_main_context_iteration () from
> /lib/libglib-2.0.so.0
> #40 0x00007ffff67fb22d in gtk_main_iteration_do () from
> /usr/lib/libgtk-x11-2.0.so.0
> #41 0x00007ffff6d5ba57 in do_iteration (do_not_block=<value optimized
> out>, do_not_sleep=false) at main.cpp:502
> #42 0x00007ffff6d5be96 in my_loop () at main.cpp:430
> #43 0x000000000043d400 in main (argc=1, argv=0x7fffffffe2f8) at gbx.c:371
> 
> Doesn't make any sense to me, but hopefully it will to you. I removed my
> project that I linked to earlier, so let me know if you still need it.

I need then that you run your project with the valgrind tool:

$ cd /yyyy/Sanctimonia
$ valgrind --tool=memcheck --num-callers=50 gbx3

Send me the output printed by valgrind.

Regards,

-- 
Beno?t Minisini



From kevinfishburne at ...590...  Sun Dec 19 19:25:23 2010
From: kevinfishburne at ...590... (Kevin Fishburne)
Date: Sun, 19 Dec 2010 13:25:23 -0500
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <201012190357.57038.gambas@...1...>
References: <4D0C192B.4060602@...590...>	<201012181946.26057.gambas@...1...>	<4D0D3FAD.40803@...590...>
	<201012190357.57038.gambas@...1...>
Message-ID: <4D0E4E13.2000408@...590...>

On 12/18/2010 09:57 PM, Beno?t Minisini wrote:
> I need then that you run your project with the valgrind tool:
>
> $ cd /yyyy/Sanctimonia
> $ valgrind --tool=memcheck --num-callers=50 gbx3
>
> Send me the output printed by valgrind.
I've been repeatedly running the project with valgrind for the last few 
hours. It ran successfully every time except for one, though the 
valgrind output showed nothing of interest other than what it noted 
during successful runs. I'm not sure if it crashed that one time or if 
some other error occurred. When/if the app crashes, will it disappear 
from the screen, thus letting me know it has crashed?

I've attached my terminal history containing valgrind's output for the 
last few runs, just in case there's something insightful in there. There 
are some errors which appear to be related to some form controls or 
variables not being freed properly.

-- 
Kevin Fishburne
Eight Virtues
www: http://sales.eightvirtues.com
e-mail: sales at ...590...
phone: (770) 853-6271

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: valgrind output
URL: <http://lists.gambas-basic.org/pipermail/devel/attachments/20101219/ce85de50/attachment.ksh>

From gambas at ...1...  Mon Dec 20 04:18:09 2010
From: gambas at ...1... (=?utf-8?q?Beno=C3=AEt_Minisini?=)
Date: Mon, 20 Dec 2010 04:18:09 +0100
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <4D0E4E13.2000408@...590...>
References: <4D0C192B.4060602@...590...>
	<201012190357.57038.gambas@...1...>
	<4D0E4E13.2000408@...590...>
Message-ID: <201012200418.09079.gambas@...1...>

> On 12/18/2010 09:57 PM, Beno?t Minisini wrote:
> > I need then that you run your project with the valgrind tool:
> > 
> > $ cd /yyyy/Sanctimonia
> > $ valgrind --tool=memcheck --num-callers=50 gbx3
> > 
> > Send me the output printed by valgrind.
> 
> I've been repeatedly running the project with valgrind for the last few
> hours. It ran successfully every time except for one, though the
> valgrind output showed nothing of interest other than what it noted
> during successful runs. I'm not sure if it crashed that one time or if
> some other error occurred. When/if the app crashes, will it disappear
> from the screen, thus letting me know it has crashed?
> 
> I've attached my terminal history containing valgrind's output for the
> last few runs, just in case there's something insightful in there. There
> are some errors which appear to be related to some form controls or
> variables not being freed properly.

No information there. I need a valgrind output when the program crashes.

When the program does an illegal memory access, valgrind does not necessarily 
stops it as the kernel does. It ignores it, displays the error, and tries to 
continue. When it really cannot continue, it stops and dumps a "vgcore" file.

You must find a way to reproduce the crash, and then run valgrind to get the 
information on it.

Regards,

-- 
Beno?t Minisini



From kevinfishburne at ...590...  Mon Dec 20 05:11:08 2010
From: kevinfishburne at ...590... (Kevin Fishburne)
Date: Sun, 19 Dec 2010 23:11:08 -0500
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <201012200418.09079.gambas@...1...>
References: <4D0C192B.4060602@...590...>	<201012190357.57038.gambas@...1...>	<4D0E4E13.2000408@...590...>
	<201012200418.09079.gambas@...1...>
Message-ID: <4D0ED75C.1000904@...590...>

On 12/19/2010 10:18 PM, Beno?t Minisini wrote:
> No information there. I need a valgrind output when the program crashes.
>
> When the program does an illegal memory access, valgrind does not necessarily
> stops it as the kernel does. It ignores it, displays the error, and tries to
> continue. When it really cannot continue, it stops and dumps a "vgcore" file.
>
> You must find a way to reproduce the crash, and then run valgrind to get the
> information on it.
I understand; good info. I am beginning to suspect that the crash only 
occurs on subsequent runs within a GAMBAS IDE session, but not on the 
first run. It happens pretty frequently while developing it, but doesn't 
seem to have happened once while using valgrind. I noticed that the 
valgrind command doesn't bring up the GAMBAS IDE, but runs the app 
directly. Is there a way to get valgrind to just bring up the GAMBAS IDE 
so I can continually start and stop the app until it crashes?

Just guessing here, but based on the amount of time that elapses before 
it crashes it appears that the crash is related to either a DrawingArea 
control or the Image.Draw method. It happened before the DrawAlpha 
method, so that is ruled out. I may try setting a breakpoint right 
before the graphics are rendered and stepping through the code with F8 
to identify the crash point. That would at least narrow it down should 
the crash not occur using valgrind.

-- 
Kevin Fishburne
Eight Virtues
www: http://sales.eightvirtues.com
e-mail: sales at ...590...
phone: (770) 853-6271




From gambas at ...1...  Mon Dec 20 05:16:20 2010
From: gambas at ...1... (=?utf-8?q?Beno=C3=AEt_Minisini?=)
Date: Mon, 20 Dec 2010 05:16:20 +0100
Subject: [Gambas-devel] signal 11 when rendering graphics using gb.image
In-Reply-To: <4D0ED75C.1000904@...590...>
References: <4D0C192B.4060602@...590...>
	<201012200418.09079.gambas@...1...>
	<4D0ED75C.1000904@...590...>
Message-ID: <201012200516.20842.gambas@...1...>

> On 12/19/2010 10:18 PM, Beno?t Minisini wrote:
> > No information there. I need a valgrind output when the program crashes.
> > 
> > When the program does an illegal memory access, valgrind does not
> > necessarily stops it as the kernel does. It ignores it, displays the
> > error, and tries to continue. When it really cannot continue, it stops
> > and dumps a "vgcore" file.
> > 
> > You must find a way to reproduce the crash, and then run valgrind to get
> > the information on it.
> 
> I understand; good info. I am beginning to suspect that the crash only
> occurs on subsequent runs within a GAMBAS IDE session, but not on the
> first run. It happens pretty frequently while developing it, but doesn't
> seem to have happened once while using valgrind. I noticed that the
> valgrind command doesn't bring up the GAMBAS IDE, but runs the app
> directly. Is there a way to get valgrind to just bring up the GAMBAS IDE
> so I can continually start and stop the app until it crashes?
> 
> Just guessing here, but based on the amount of time that elapses before
> it crashes it appears that the crash is related to either a DrawingArea
> control or the Image.Draw method. It happened before the DrawAlpha
> method, so that is ruled out. I may try setting a breakpoint right
> before the graphics are rendered and stepping through the code with F8
> to identify the crash point. That would at least narrow it down should
> the crash not occur using valgrind.

The IDE is not really needed (well, it *should* not). The only difference is 
that the IDE run the interpreter in debugging mode.

So, do that instead, to see if you get a crash inside valgrind:

$ cd /yyyy/Sanctimonia
$ valgrind --tool=memcheck --num-callers=50 gbx3 -g

And when you get the interpreter debugger prompt, type "g" + RETURN.

-- 
Beno?t Minisini



From gambas.fr at ...176...  Tue Dec 21 15:46:27 2010
From: gambas.fr at ...176... (Fabien Bodard)
Date: Tue, 21 Dec 2010 15:46:27 +0100
Subject: [Gambas-devel] New IconView
In-Reply-To: <AANLkTinOZp85hFYqEyZN09G1MHPQW02RauL3F9Pck9fh@...178...>
References: <AANLkTinOZp85hFYqEyZN09G1MHPQW02RauL3F9Pck9fh@...178...>
Message-ID: <AANLkTi=ayx2=NmjajxiCU11bFfzgJ_hNpnXe5v8nYAKv@...178...>

maj

2010/12/21 Fabien Bodard <gambas.fr at ...176...>:
> I'm currently working on a new iconview widget in gambas , to replace
> the current gtk and qt ones.
>
> this can you all test it ? (use the last rev) and repport me all the
> problem you see
>
> there is a known bug on the mouse rect selection, and i've not wrote
> the Drag&Drop part.
>
>
>
> Bonus: there is a Picture property ! To setup the background
>
> --
> Fabien Bodard
>



-- 
Fabien Bodard



From gambas.fr at ...176...  Tue Dec 21 23:12:23 2010
From: gambas.fr at ...176... (Fabien Bodard)
Date: Tue, 21 Dec 2010 23:12:23 +0100
Subject: [Gambas-devel] IconView
Message-ID: <AANLkTikwasT583+v8JR-HUqqMEFLU_-h96v8KcYW-jqd@...178...>

Hi to all

This is a new widget ... an icon view to replace the buggy native qt/gtk one

Mine in buggy too ... but i can correct my own bugs easily... as it is
entirely writted in gambas.

It miss the search keys (what did you prefer ... textbox at bottom
right like gnome , or qt mode ?)

the mouse sel square have a bug ... i'm still searching where i've
made an error :/... certainly a stupid one :)

i need your improve... please tel me what is bad or good ... quickly
so we can add it to the 3th release.

If you need some special feature ... tell us to ... and we will advise.

I've already added a background property, It miss Drag and drop ...
not yet implemented



PS Sorry for my too bad english



-- 
Fabien Bodard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gb.form.widgets-0.1.tar.gz
Type: application/x-gzip
Size: 26788 bytes
Desc: not available
URL: <http://lists.gambas-basic.org/pipermail/devel/attachments/20101221/46b82ce8/attachment.bin>

From ron at ...572...  Fri Dec 31 11:21:47 2010
From: ron at ...572... (Ron)
Date: Fri, 31 Dec 2010 11:21:47 +0100
Subject: [Gambas-devel] System error... (42)
In-Reply-To: <AANLkTinZnDLDrfT8c15i63Ww2GUm16Yig+wguzQT-JCZ@...178...>
References: <AANLkTi=K32BLTv73_x7M0DcDP=RomDBPn=66QSRcBLFC@...178...>
	<201012051205.33577.gambas@...1...>
	<AANLkTinZnDLDrfT8c15i63Ww2GUm16Yig+wguzQT-JCZ@...178...>
Message-ID: <AANLkTi=D77uT=t6g+L5Uf0MLagTDngtiD4m43jM_8Tkc@...178...>

Beno?t,

trying to debug this problem, but if I follow your instructions, I get
this right away.. are you sure they are correct?

on at ...218...:~/domotiga/DomotiGaServer$ gdb gbx2
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/bin/gbx2...done.
(gdb) break THROW
Breakpoint 1 at 0x804be2e: file gb_error.c, line 273.
(gdb) run
Starting program: /usr/local/bin/gbx2
[Thread debugging using libthread_db enabled]

Breakpoint 1, THROW (code=13) at gb_error.c:273
273	void THROW(int code, ...)
(gdb) bt
#0  THROW (code=13) at gb_error.c:273
#1  0x08057162 in get_stream (value=0x807fad0, can_default=<value
optimized out>) at gbx_subr_file.c:146
#2  0x0805717c in SUBR_close () at gbx_subr_file.c:187
#3  0x0806b0f3 in EXEC_loop () at gbx_exec_loop.c:476
#4  0x0804f533 in EXEC_function_loop () at gbx_exec.c:703
#5  0x0804f809 in EXEC_function_real () at gbx_exec.c:690
#6  0x08061c29 in main (argc=134739048, argv=0xbffff544) at gbx.c:349

I guess it stops at every error now, even known ones...

Regards,
Ron_2nd.

On Sun, Dec 5, 2010 at 12:11 PM, Ron <ron at ...572...> wrote:
> Haven't been able to reproduce it yet.
> I didn't change a lot to my code, so maybe it was just a one in a
> million things...
> Checked my dmesg for weird system/hardware problems, but no sign off any.
> Will keep you posted if it happens again...
>
> It is on Gambas2, latest rev.
>
> Regards,
> Ron_2nd.
> 2010/12/5 Beno?t Minisini <gambas at ...1...>:
>>> Ok. Sometime things get weird...
>>>
>>> I found that my command line project wasn't running anymore...
>>>
>>> 2010/12/04 15:42:16 You have 2 new e-mails on Gmail.
>>> 2010/12/04 15:47:16 Uploaded sensor data to Bwired.
>>> 2010/12/04 15:47:21 Uploaded sensor data to Pachube.
>>> 2010/12/04 16:00:00 The Time of Day is afternoon.
>>> 2010/12/04 16:00:00 It's dark outside.
>>> 2010/12/04 16:00:00 DomotiGa is running for 0 days, 4 hrs, 12 mins, and 43
>>> secs. 2010/12/04 16:02:21 Uploaded sensor data to Pachube.
>>> ERROR: #42: System error. Success
>>>
>>> System error... (42)
>>> This error is raised when a system call returns an error that does not
>>> match another specific Gambas error.
>>>
>>> Hmm ok, no clue... yes it's a Linux system, although the error message
>>> has a Windows logic in it.
>>>
>>> Regards,
>>> Ron_2nd.
>>>
>>
>> Can you run your command line tool that way to know where the error comes
>> from?
>>
>> $ gdb gbx2
>> ...
>> (gdb) break THROW
>> ...
>> (gdb) run
>> ...
>> ... Let your program run until it stops
>> ...
>> (gdb) bt
>> ...
>>
>> Then send me the result of the 'bt' gdb command.
>>
>> Be sure that you have a Gambas 2 compiled with debugging symbols enabled.
>>
>> And if you use Gambas 3 instead of Gambas 2, replace "gbx2" by "gbx3".
>>
>> Regards,
>>
>> --
>> Beno?t Minisini
>>
>> ------------------------------------------------------------------------------
>> What happens now with your Lotus Notes apps - do you make another costly
>> upgrade, or settle for being marooned without product support? Time to move
>> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
>> use, and manage than apps on traditional platforms. Sign up for the Lotus
>> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
>> _______________________________________________
>> Gambas-devel mailing list
>> Gambas-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gambas-devel
>>
>



From gambas at ...1...  Fri Dec 31 14:40:16 2010
From: gambas at ...1... (=?utf-8?q?Beno=C3=AEt_Minisini?=)
Date: Fri, 31 Dec 2010 14:40:16 +0100
Subject: [Gambas-devel] System error... (42)
In-Reply-To: <AANLkTi=D77uT=t6g+L5Uf0MLagTDngtiD4m43jM_8Tkc@...178...>
References: <AANLkTi=K32BLTv73_x7M0DcDP=RomDBPn=66QSRcBLFC@...178...>
	<AANLkTinZnDLDrfT8c15i63Ww2GUm16Yig+wguzQT-JCZ@...178...>
	<AANLkTi=D77uT=t6g+L5Uf0MLagTDngtiD4m43jM_8Tkc@...178...>
Message-ID: <201012311440.17016.gambas@...1...>

> Beno?t,
> 
> trying to debug this problem, but if I follow your instructions, I get
> this right away.. are you sure they are correct?
> 
> on at ...218...:~/domotiga/DomotiGaServer$ gdb gbx2
> GNU gdb (GDB) 7.1-ubuntu
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html> This is free software: you are free to
> change and redistribute it. There is NO WARRANTY, to the extent permitted
> by law.  Type "show copying" and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/local/bin/gbx2...done.
> (gdb) break THROW
> Breakpoint 1 at 0x804be2e: file gb_error.c, line 273.
> (gdb) run
> Starting program: /usr/local/bin/gbx2
> [Thread debugging using libthread_db enabled]
> 
> Breakpoint 1, THROW (code=13) at gb_error.c:273
> 273	void THROW(int code, ...)
> (gdb) bt
> #0  THROW (code=13) at gb_error.c:273
> #1  0x08057162 in get_stream (value=0x807fad0, can_default=<value
> optimized out>) at gbx_subr_file.c:146
> #2  0x0805717c in SUBR_close () at gbx_subr_file.c:187
> #3  0x0806b0f3 in EXEC_loop () at gbx_exec_loop.c:476
> #4  0x0804f533 in EXEC_function_loop () at gbx_exec.c:703
> #5  0x0804f809 in EXEC_function_real () at gbx_exec.c:690
> #6  0x08061c29 in main (argc=134739048, argv=0xbffff544) at gbx.c:349
> 
> I guess it stops at every error now, even known ones...
> 
> Regards,
> Ron_2nd.
> 

This is not your error (42). THROW is raised a lot of time, but you may not 
see it because a TRY or a CATCH can intercept it, or because the interpreter 
internally catches it.

To catch only system errors. Add that to the THROW() function, in gb_error.c, 
at line 278:

	if (code == 42) BREAKPOINT();

Compile and install again.

Then run your program into gdb until it stops at that line.

Once done, don't forget to remove that line, otherwise your program will stop 
at that line even outside of the debugger.

Regards,





-- 
Beno?t Minisini