Serialization on os x returns (SIGTRAP)

Question

Hello everyone!
I'm writing an os x application that calculates scores for a local swim team, and then stores them along with other information about swimmers and the team. I'm using apple's appkit, a series of java classes meant to work with their InterfaceBuilder program. The problem i run into is when i try to save one NSMutableArray object [which does implement serializable from everything i read on it]. No exeptions are thrown when i look at the run log, but i get a (SIGTRAP) signal, which from what i can find is a trace/breakpoint error. I load the program into the debugger and can see that in the thread 1 the last things to happen are
0 objctrap
1 objcerror
2 __objc_error
I think these relate to the SIGTRAP signal, but to be honest i don't have enough experience with this to be able to decipher what it's trying to tell me. The SIGTRAP terminates the method and creates a core file of what the program is trying to save, i think, because there is a file after the program crashes, but when you try and look at it in a text editor it appears blank or very little in it that i can't really identify. Anyways, these are the methods that are called when someone presses the save/open button.
Method is called to save document
     public void writeToFile(String filePathName)
          FileOutputStream fos = null;
          ObjectOutputStream out = null;
          try
               //create a stream to the output file
               fos = new FileOutputStream(filePathName);
               //create an object output stream
               out = new ObjectOutputStream(fos);
               //write the data
               out.writeObject(objectToBeSaved);
               //close the streams
               out.close();
               fos.close();
          catch(IOException ex)
               ex.printStackTrace();
     }method is called to open document
     public NSMutableArray readFromFile(String fileOpenPath)
          //declare variables
          NSMutableArray arrayToReturn = new NSMutableArray();
          FileInputStream fis = null;
          ObjectInputStream in = null;
          try
               //Create a stream from the input file
               fis = new FileInputStream(fileOpenPath);
               //Create an object input stream
               in = new ObjectInputStream(fis);
               //read the data
               arrayToReturn = (NSMutableArray) in.readObject();
               //close the streams
               in.close();
               fis.close();
          catch(IOException ex)
               ex.printStackTrace();
          catch(ClassNotFoundException ex)
               ex.printStackTrace();
          /*  Already been caught error???
          catch(FileNotFoundException ex)
               ex.printStackTrace();
          return arrayToReturn;
     }also if you refer to the commented portion of the open method, i commented out catching the FileNotFoundException because i got an 'FileNotFoundException already caught' error. Either way, any insight into what the (SIGTRAP) signal actually is [i think it refers to memory management?] or why i'm getting it would be great. duke dollars if i actually fix the problem, thanks to all in advance!

Answer 1

I've now tried the following:
public void doit() {
Runnable getTextFieldText = new Runnable() {
public void run() {
System.out.println("%%%%%%%%%%%%%%%%%%%%%%%%%% 1 "+ SwingUtilities.isEventDispatchThread() );
JFileChooser chooser = new JFileChooser();
System.out.println("%%%%%%%%%%%%%%%%%%%%%%%%%% 2 "+ SwingUtilities.isEventDispatchThread() );
chooser.setCurrentDirectory(new File(System.getProperty("user.home")+"/Desktop/"));
System.out.println("%%%%%%%%%%%%%%%%%%%%%%%%%% 3 "+ SwingUtilities.isEventDispatchThread() );
chooser.setSelectedFile(new File("fred"));
System.out.println("%%%%%%%%%%%%%%%%%%%%%%%%%% 4 "+ SwingUtilities.isEventDispatchThread() );
chooser.setDialogTitle("Save Attachment - ");
System.out.println("%%%%%%%%%%%%%%%%%%%%%%%%%% 5 "+ SwingUtilities.isEventDispatchThread() );
int returnVal = chooser.showSaveDialog(null);
System.out.println("@@@@@@@@@@@@@@@@@@@@@@@@@@@@ "+returnVal);
try{
SwingUtilities.invokeLater(getTextFieldText);
}catch(Exception x){
x.printStackTrace();
Which works everywhere except FF which hang after the user dismisses the dialog. I'm begging for any insight here.