After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640302 - vala segfaults if string template is used as argument to Bus.get_proxy_sync
vala segfaults if string template is used as argument to Bus.get_proxy_sync
Status: RESOLVED OBSOLETE
Product: vala
Classification: Core
Component: D-Bus
0.11.x
Other All
: Normal normal
: 1.0
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-23 01:52 UTC by Łukasz Pankowski
Modified: 2018-05-22 13:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
benchmark triggering valac segfault (471 bytes, application/octet-stream)
2011-01-23 01:52 UTC, Łukasz Pankowski 		Details

Description Łukasz Pankowski 2011-01-23 01:52:10 UTC 
Created attachment 179063 [details]
benchmark triggering valac segfault

This is segfault on a valid code.
Each of the following calls (part of attached vala file triggering the error):

    // each of following lines segfaults valac
    o = Bus.get_proxy_sync(BusType.SESSION, @"org.freedesktop.DBus", "/");
    o = Bus.get_proxy_sync(BusType.SESSION, "org.freedesktop.DBus", @"/");

It segfaults for valac 0.10.0, 0.10.4 and 0.10.5.
Here is gdb backtrace of segfaulting compilation using valac 0.11.5:

$ LANG=C gdb --silent --args valac --pkg gio-2.0 segfault.vala
Reading symbols from /home/lupan/local/bin/valac...done.
(gdb) r
Starting program: /home/lupan/local/bin/valac --pkg gio-2.0 segfault.vala
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0xb7d4fc4c in vala_data_type_get_actual_type (self=0x0, derived_instance_type=0x0, method_access=0x8a0ac08, node_reference=0x8a01140) at valadatatype.c:1778
1778		return VALA_DATA_TYPE_GET_CLASS (self)->get_actual_type (self, derived_instance_type, method_access, node_reference);
(gdb) bt

+ Trace 225653

  • #0 vala_data_type_get_actual_type
    at valadatatype.c line 1778
  • #1 vala_method_call_real_check
    at valamethodcall.c line 3709
  • #2 vala_code_node_check
    at valacodenode.c line 415
  • #3 vala_assignment_real_check
    at valaassignment.c line 2188
  • #4 vala_code_node_check
    at valacodenode.c line 415
  • #5 vala_expression_statement_real_check
    at valaexpressionstatement.c line 351
  • #6 vala_code_node_check
    at valacodenode.c line 415
  • #7 vala_block_real_check
    at valablock.c line 1848
  • #8 vala_code_node_check
    at valacodenode.c line 415
  • #9 vala_method_real_check
    at valamethod.c line 4015
  • #10 vala_code_node_check
    at valacodenode.c line 415
  • #11 vala_source_file_check
    at valasourcefile.c line 967
  • #12 vala_semantic_analyzer_real_visit_source_file
    at valasemanticanalyzer.c line 2137
  • #13 vala_code_visitor_visit_source_file
    at valacodevisitor.c line 1329
  • #14 vala_source_file_accept
    at valasourcefile.c line 402
  • #15 vala_code_context_accept
    at valacodecontext.c line 1085
  • #16 vala_semantic_analyzer_analyze
    at valasemanticanalyzer.c line 2127
  • #17 vala_code_context_check
    at valacodecontext.c line 1104
  • #18 vala_compiler_run
    at valacompiler.c line 709
  • #19 vala_compiler_main
    at valacompiler.c line 1269
  • #20 main
    at valacompiler.c line 1277 






Comment 1


GNOME Infrastructure Team





          2018-05-22 13:52:28 UTC
        



-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vala/issues/159.