Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #13503 > unrolled thread

Java JDesktop GUI Segmentation Fault on first use in CDE (Solaris 10) Until I Logout and Log Back in

Back to article view | Back to comp.lang.java.programmer

Contents

  Java JDesktop GUI Segmentation Fault on first use in CDE (Solaris 10) Until I Logout and Log Back in brianjester@gmail.com - 2012-04-12 14:18 -0700
    Re: Java JDesktop GUI Segmentation Fault on first use in CDE (Solaris 10) Until I Logout and Log Back in Patricia Shanahan <pats@acm.org> - 2012-04-12 14:41 -0700
      Re: Java JDesktop GUI Segmentation Fault on first use in CDE (Solaris 10) Until I Logout and Log Back in Brian Jester <brianjester@gmail.com> - 2012-04-16 13:56 -0700
        Re: Java JDesktop GUI Segmentation Fault on first use in CDE (Solaris 10) Until I Logout and Log Back in Roedy Green <see_website@mindprod.com.invalid> - 2012-05-14 21:48 -0700

#13503 — Java JDesktop GUI Segmentation Fault on first use in CDE (Solaris 10) Until I Logout and Log Back in

I have a Java Jdesktop GUI created in Netbeans 7.0.1 and the target architecture in sun4u/sun4v with Solaris 10 and CDE when I attempt to run it for the first time after installing it with pkgadd it crashes:

  pkgadd -d myAppPkg

  java -jar myApp.jar

I get:

  Segmentation Fault - core dumped

If I log out and log in, the problem goes away and I can launch the Jar just fine and the GUI appears.

Any ideas?

Thank you,

Brian

[toc] | [next] | [standalone]

#13504

On 4/12/2012 2:18 PM, brianjester@gmail.com wrote:
> I have a Java Jdesktop GUI created in Netbeans 7.0.1 and the target architecture in sun4u/sun4v with Solaris 10 and CDE when I attempt to run it for the first time after installing it with pkgadd it crashes:
>
>    pkgadd -d myAppPkg
>
>    java -jar myApp.jar
>
> I get:
>
>    Segmentation Fault - core dumped
>
> If I log out and log in, the problem goes away and I can launch the Jar just fine and the GUI appears.
>
> Any ideas?

Perhaps it could be a multi-threading race condition. The different
history could affect which operations are slowed down by page faults due
to libraries not being in memory.

Patricia

[toc] | [prev] | [next] | [standalone]

#13591

Patricia,

Anything I might try to keep it from faulting?  

Brian

[toc] | [prev] | [next] | [standalone]

#14540

On Mon, 16 Apr 2012 13:56:58 -0700 (PDT), Brian Jester
<brianjester@gmail.com> wrote, quoted or indirectly quoted someone who
said :

>Anything I might try to keep it from faulting?  

If you have threads:

1. try to replace anything you can with java.util.concurrent library
code.

2. go through any threading code line by line imagining some other
thread like a jittery puppy trying to interfere.

3. remove the threading and add it back a little at a time.

4. run the code in a debugger. It may tell you more about where the
trouble is happening.
-- 
Roedy Green Canadian Mind Products
http://mindprod.com
Programmers love to create simplified replacements for HTML. 
They forget that the simplest language is the one you 
already know. They also forget that their simple little 
markup language will bit by bit become even more convoluted 
and complicated than HTML because of the unplanned way it grows.
.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web