#25 GUI-Crashes in FWBuilder build-2513

closed-fixed
Vadim Kurland
None
1
2010-03-10
2010-02-11
schommski
No

Hi,

I experienced a couple of crashes in the lastest builds of fwbuilder4:
As soon as I open up a policy of one of my firewalls I'm no longer able to change or create objects of any kind, for instance: when I'm trying to add a host to a host-group that I selected by double-clicking the object in the policy-grid, the GUI immediatly crashes with a segmentation fault. This only happens if the policy has a minimum two entries (at least during my tests it happens after the second rule has been inserted).

Here are the steps to re-enact what lead to my problem:
First, for NOT crashing the GUI, it is crucial for the following steps that you don't have any policy opened up after loading the .fwb-file.
1) run 'fwbuilder debug-policy.fwb'
2) Create a new Group under /User/Objects/Groups
3) Rename the newly created Group to e.g. 'DNS-Servers' (the name doesn't really matter)
4) Add Hosts dns1 and dns2 to the 'DNS-Servers'-Group
Result: Everything works as expected.

Here are the steps that lead to the crash:
1) run 'fwbuilder debug-policy.fwb'
2) Create a few new hosts, in my example 'ldap-server1' and 'ldap-server2'
3) Now, open the policy of Firewall test-fw1 by double-clicking /User/Firewalls/test-fw1/Policy
4) In the object-tree, double-click on group 'LDAP-Servers' and add both host-objects 'ldap-server1' and 'ldap-server2' by dragging them onto the list-view
Result: Segmentation fault

Currently I'm running FWbuilder4 build-2513 on Ubuntu 9.10 32bit. These GUI crashes seem to appear an all platforms (Mac OS X 10.6, Windows XP, Ubuntu 9.10, all 32bit that I tested so far) with different fwb-files. I already tried running 'fwbedit checktree -f debug-policy.fwb', as well as moving objects to a new file in order to avoid provoking those crashes due to an erroneous XML-Structure, but nothing helped. Therefore I created a completely new file and tried to re-enact all the steps that lead to a segfault. That file (debug-policy.fwb) and some gdb-output is attached to this artifact, I hope it helps to shed some light on this issue.

Thank you very much for time and help (and fwbuilder, of course ;).

-Chris

Discussion

  • schommski
    schommski
    2010-02-11

    sample fwb-file and gdb backtraces

     
  • Vadim Kurland
    Vadim Kurland
    2010-02-11

    acknowledged, will fix today.

     
  • Vadim Kurland
    Vadim Kurland
    2010-02-11

    • assigned_to: nobody --> vkurland
     
  • Vadim Kurland
    Vadim Kurland
    2010-02-12

    • priority: 5 --> 1
    • status: open --> open-fixed
     
  • Vadim Kurland
    Vadim Kurland
    2010-02-12

    this is fixed in build 2516 or later

     
  • Vadim Kurland
    Vadim Kurland
    2010-03-10

    • status: open-fixed --> closed-fixed