[Gambas-user] Issue 393 in gambas: Signal 11 in JSON.Decode
gambas at ...2524...
gambas at ...2524...
Thu Jan 24 11:47:18 CET 2013
Status: New
Owner: ----
Labels: Version Type-Bug Priority-Medium OpSys-Any Dist-Any Arch-Any
Desktop-Any GUI-Any
New issue 393 by r... at ...1740...: Signal 11 in JSON.Decode
http://code.google.com/p/gambas/issues/detail?id=393
1) Describe the problem.
When using JSON.Decode Gambas3 segfaults
2) GIVE THE FOLLOWING INFORMATIONS (if they are appropriate):
Version: TRUNK
Revision: r5514
Operating system: Linux
Distribution: Ubuntu 11.04
Architecture: x86_64
GUI component: QT4
Desktop used: Gnome
3) Provide a little project that reproduces the bug or the crash.
Attached
5) Explain clearly how to reproduce the bug or the crash.
Run attached project, see this gdb bt output:
~/development/bugreports/Jsonsignal11$ gdb gbx3
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
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 "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/gbx3...done.
(gdb) run
Starting program: /usr/bin/gbx3
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
ARRAY_add_data (p_data=0x67bff8, num=2, zero=1 '\001')
at ../share/gb_array_temp.h:68
68 array->count += num;
(gdb) bt
#0 ARRAY_add_data (p_data=0x67bff8, num=2, zero=1 '\001')
at ../share/gb_array_temp.h:68
#1 0x000000000042ce5c in _convert (src=0x83c6b8, class=<value optimized
out>, conv=0x7ffff630d060) at gbx_c_array.c:1426
#2 0x00000000004072de in VALUE_convert (value=0x7ffff630d060,
type=6689736) at gbx_value.c:861
#3 0x0000000000436a47 in EXEC_loop () at gbx_exec_loop.c:625
#4 0x0000000000409d6b in EXEC_function_loop () at gbx_exec.c:906
#5 0x000000000040a437 in EXEC_function_real () at gbx_exec.c:870
#6 0x000000000041fc65 in raise_event (observer=<value optimized out>,
object=<value optimized out>, func_id=<value optimized out>, nparam=<value
optimized out>) at gbx_api.c:810
#7 0x000000000042040d in GB_Raise (object=0x835f28, event_id=21, nparam=0)
at gbx_api.c:946
#8 0x00007ffff5cae81e in gMainWindow::emitOpen (this=0x835ff0) at
gmainwindow.cpp:445
#9 0x00007ffff5cae880 in gMainWindow::setVisible (this=<value optimized
out>, vl=<value optimized out>) at gmainwindow.cpp:475
#10 0x000000000040ab82 in EXEC_native () at gbx_exec.c:1332
#11 0x000000000040b155 in EXEC_public_desc (class=<value optimized out>,
object=<value optimized out>, desc=<value optimized out>, nparam=<value
optimized out>) at gbx_exec.c:1572
#12 0x0000000000426012 in main (argc=1, argv=0x7fffffffe3c8) at gbx.c:390
(gdb)
6) By doing that carefully, you have done 50% of the bug fix job!
IMPORTANT NOTE: if you encounter several different problems or bugs, (for
example, a bug in your project, and an interpreter crash while debugging
it), please create distinct issues!
Attachments:
Jsonsignal11-0.0.1.tar.gz 604 KB
More information about the User
mailing list