bugGNUstep - Bugs: bug #29718, Gorm: Segmenation fault after...

Group
 
 

bug #29718: Gorm: Segmenation fault after loading NIB file (nib created with Gorm)

Submitter:  Fred Kiefer <FredKiefer>
Submitted:  Thu 29 Apr 2010 08:45:59 PM UTC
   
 
Category:  Gorm Severity:  3 - Normal
Item Group:  Bug Status:  Wont Fix
Privacy:  Public Assigned to:  gcasa
Open/Closed:  Declined
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 01 Jan 2023 01:32:49 AM UTC, comment #5: 

This issue will not be fixed since saving nib files will be removed from the next version of Gorm.  Also nib files are no longer in use on macOS.

Gregory John Casamento <gcasa>
Group administrator
Thu 06 May 2010 08:28:15 AM UTC, comment #4: 

I am using a 64 Linux system myself (see bug report below), so this isn't the difference. Today I had load the busybox.nib files five times to get the issue. Be sure to have the inspector visible and click on the loaded window once. This seems to help in reproducing the bug.

Fred Kiefer <FredKiefer>
Group Member
Thu 06 May 2010 08:04:38 AM UTC, comment #3: 

I am able to run gormtest.app with busybox.nib as it's test nib just fine.  See the attached image.  I tried it a number of times and couldn't get it to crash.  This might be because I'm using a 64 bit system, though.  I'll try it on one of the 32 bit systems I have here.


Gregory John Casamento <gcasa>
Group administrator
Thu 06 May 2010 07:28:42 AM UTC, comment #2: 

As I wrote in a private mail, I was able to reproduce this issue by loading the busybox example NIB file from the gormtest project. The files there look as if they where written on a Mac system, at least the plist doc type points to Apple.

Have you been able to reproduce this behaviour? Has anybody?

Fred Kiefer <FredKiefer>
Group Member
Thu 06 May 2010 12:57:40 AM UTC, comment #1: 

It is important to remember that Gorm's nib creation is incomplete.   I will investigate this, but a more valid test is to see if it loads nibs created with OS X. 

GC

Gregory John Casamento <gcasa>
Group administrator
Thu 29 Apr 2010 08:45:59 PM UTC, original submission:  

System:
64 bit Linux
Current GNUstep from SVN, Current Gorm

Steps to reproduce:
- Start up Gorm
- Load a NIB file (I used the DBModel entity inspector, which I had converted from a Gorm to a NIB file).
- Make sure the inspector panel is open and click on the loaded window.
- Exit Gorm

I got a segmentation fault from these few steps.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff622d7a5 in objc_msg_lookup () from /usr/lib64/libobjc.so.2
(gdb) bt                                                            
#0  0x00007ffff622d7a5 in objc_msg_lookup () from /usr/lib64/libobjc.so.2
#1  0x00007ffff6fe5d73 in -[NSWindow resignKeyWindow] (self=0x1369ba0, _cmd=<value optimized out>)
    at NSWindow.m:1787                                                                           
#2  0x00007ffff6e8c233 in -[NSApplication deactivate] (self=0x840f00, _cmd=<value optimized out>)
    at NSApplication.m:1336                                                                      
#3  0x00007ffff31d039c in -[XGServer(EventOps) processEvent:] (self=0x861d30, _cmd=<value optimized out>,
    event=<value optimized out>) at XGServerEvent.m:1143                                                 
#4  0x00007ffff31cc58b in -[XGServer(EventOps) receivedEvent:type:extra:forMode:] (self=0x861d30,        
    _cmd=<value optimized out>, data=<value optimized out>, type=<value optimized out>,                  
    extra=<value optimized out>, mode=<value optimized out>) at XGServerEvent.m:309                      
#5  0x00007ffff69527d3 in -[GSRunLoopCtxt pollUntil:within:] (self=0x8a9a40, _cmd=<value optimized out>, 
    milliseconds=<value optimized out>, contexts=0x89cfb0) at GSRunLoopCtxt.m:488  

It turned out that the first responder of that window had a "deadface" isa pointer. Running the same application once more with a breakpoint on [NSWindow makeFirstResponder:] showed that the object in question was a GormWindowEditor.

po aResponder
 h=--- v=--- <GormWindowEditor: 0x1372170> f={x = 0; y = 0; width = 0; height = 0} b={x = 0; y = 0; width = 0; height = 0}

I expect that this problem is triggered by the changed handling of retains for Gorm/NIB loading in gui. It is well possible that an existing bug got triggered by that change or that this change itself still has issues.

Fred Kiefer <FredKiefer>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #20463:  busybox_test.png added by gcasa (106KiB - image/png - Busybox test... )

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gcasa (Posted a comment)
  • -email is unavailable- added by FredKiefer (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-01-01 gcasa StatusIn Progress Wont Fix
        Open/ClosedOpen Declined
    2010-05-06 gcasa Attached File- Added busybox_test.png, #20463
    2010-05-06 gcasa StatusNone In Progress
        Assigned toNone gcasa
        SummaryGorm: Segmenation fault after loading NIB file Gorm: Segmenation fault after loading NIB file (nib created with Gorm)

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code