Re: JSwat crash problem

Hi Tom,

What output is there on the application side that indicates it is 
crashing? Is there a JVM error message, or it just exits?

The JSwat log file is in your home directory, in the .jswat/var/log 
directory, assuming you're using version 3.0 or higher. Look for the 
messages.log file. Hopefully that at least has some exception stack 
trace that might indicate what went wrong.

If you're using Windows, you might try the dt_shmem transport instead. 
Maybe it will be more stable, although historically it was the reverse 
(dt_socket has always been better).

n


Tom Coupland wrote:
> Hi List,
> 
> First post, so hello to all!
> 
> Been using JSwat for a week or two quite succesfully in local, but today 
> have been trying to get the remote/attaching to work and have run into 
> problems. The connecting works fine, i start my java with the option:
> 
> -agentlib:jdwp=transport=dt_socket,address=192.168.100.154:4000,server=y
> 
> Which pauses until i click resume in the remote jswat when it starts up 
> as expected. It runs fine, until it hits a breakpoint, when both jSwat 
> and my program crash with no information. It did actually work once, but 
> about three breaks in the crash occured again.
> 
> I know thats incrediable little information to go, so can anyone tell me 
> how to configure the logging for JSwat? Had a quick look around and 
> theres no sign of one and could'nt find any information about switching 
> it on. If i can get that working it'd help allot in getting to the 
> bottom of this problem.
> 
> Any thoughts or experiences of this problem on the actual problem would 
> be appreciated as well of course.
> 
> Cheers
> 
> Tom