Bug 841118 - [abrt] gjs-1.32.0-1.fc17: SearchTable: Process /usr/bin/gjs-console was killed by signal 11 (SIGSEGV)
[abrt] gjs-1.32.0-1.fc17: SearchTable: Process /usr/bin/gjs-console was kille...
Product: Fedora
Classification: Fedora
Component: gjs (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Colin Walters
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-07-18 04:21 EDT by Peter Verthez
Modified: 2013-08-01 09:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 09:08:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: core_backtrace (179.92 KB, text/plain)
2012-07-18 04:21 EDT, Peter Verthez
no flags Details
File: backtrace (208.46 KB, text/plain)
2012-07-18 04:21 EDT, Peter Verthez
no flags Details
File: maps (36.98 KB, text/plain)
2012-07-18 04:21 EDT, Peter Verthez
no flags Details
File: dso_list (7.90 KB, text/plain)
2012-07-18 04:21 EDT, Peter Verthez
no flags Details
File: var_log_messages (4.46 KB, text/plain)
2012-07-18 04:21 EDT, Peter Verthez
no flags Details

  None (edit)
Description Peter Verthez 2012-07-18 04:21:40 EDT
libreport version: 2.0.10
abrt_version:   2.0.10
backtrace_rating: 4
cmdline:        /usr/bin/gjs-console -I /usr/share/gnome-shell/js -c 'const Main = imports.extensionPrefs.main; Main.main(ARGV);' Background_Changer@peter.verthez.skynet.be
crash_function: SearchTable
executable:     /usr/bin/gjs-console
kernel:         3.4.4-5.fc17.x86_64
pid:            21469
pwd:            /home/verthezp
time:           Wed 18 Jul 2012 09:54:40 AM CEST
uid:            1000
username:       verthezp

backtrace:      Text file, 213462 bytes
core_backtrace: Text file, 184243 bytes
dso_list:       Text file, 8085 bytes
maps:           Text file, 37863 bytes
var_log_messages: Text file, 4567 bytes



:I'm trying to write a gnome shell extension.   As part of that I'm making a preference page for which one of the preferences is a file list.   I'm modelling this as a TreeView, with an Add button next to it that opens a FileChooserDialog, and adds the selected file name in the list when OK is pressed.   
:The SIGSEGV occurs then when you try to insert the String value into that TreeView.   Apparently there is a difference in behavior between a string (literal) value and a String (Object) value.
:The following works:
:        this.store.set_value(iter, 0, "test");
:but the following fails and causes gjs-console to abort with SIGSEGV:
:        this.store.set_value(iter, 0, new String("test")); 
:As a consequence of this, it is not possible to fill the TreeView with strings that are passed from somewhere else (such as the FileChooserDialog in my example), because strings are always converted to String when passed to another method.   There seems to be no workaround.

:'LESSOPEN=||/usr/bin/lesspipe.sh %s'

:Limit                     Soft Limit           Hard Limit           Units     
:Max cpu time              unlimited            unlimited            seconds   
:Max file size             unlimited            unlimited            bytes     
:Max data size             unlimited            unlimited            bytes     
:Max stack size            8388608              unlimited            bytes     
:Max core file size        0                    unlimited            bytes     
:Max resident set          unlimited            unlimited            bytes     
:Max processes             1024                 15851                processes 
:Max open files            1024                 4096                 files     
:Max locked memory         65536                65536                bytes     
:Max address space         unlimited            unlimited            bytes     
:Max file locks            unlimited            unlimited            locks     
:Max pending signals       15851                15851                signals   
:Max msgqueue size         819200               819200               bytes     
:Max nice priority         0                    0                    
:Max realtime priority     0                    0                    
:Max realtime timeout      unlimited            unlimited            us        

:pos:	0
:flags:	0100000
:pos:	82373
:flags:	0102002
:pos:	82373
:flags:	0102002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:9:/tmp/ffii8qkUe (deleted)
:pos:	0
:flags:	0100002
:pos:	0
:flags:	02004002
Comment 1 Peter Verthez 2012-07-18 04:21:48 EDT
Created attachment 598807 [details]
File: core_backtrace
Comment 2 Peter Verthez 2012-07-18 04:21:51 EDT
Created attachment 598808 [details]
File: backtrace
Comment 3 Peter Verthez 2012-07-18 04:21:54 EDT
Created attachment 598809 [details]
File: maps
Comment 4 Peter Verthez 2012-07-18 04:21:56 EDT
Created attachment 598810 [details]
File: dso_list
Comment 5 Peter Verthez 2012-07-18 04:21:58 EDT
Created attachment 598811 [details]
File: var_log_messages
Comment 6 Peter Verthez 2012-07-18 04:30:00 EDT
More background can be found in this mail thread:
Comment 7 Fedora End Of Life 2013-07-04 00:18:21 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 8 Fedora End Of Life 2013-08-01 09:08:42 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.