Summary: | socketserver crash | ||
---|---|---|---|
Product: | UPPAAL | Reporter: | Dawn Rohm <dawn.rohm> |
Component: | Engine | Assignee: | Gerd Behrmann <behrmann> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P1 | ||
Version: | 3.6 Beta 2 | ||
Hardware: | PC | ||
OS: | Linux | ||
Architecture: |
Description
Dawn Rohm
2006-04-12 23:47:13 CEST
From your strace I notice that it fails right before the socketserver forks off the actual verification process (server). Which version of Debian do you use? And which kernel version? I tried to replicate the problem by running the socketserver on Debian stable with the 2.6.8-2-686-smp kernel provided by the distribution. The GUI ran on Windows XP SP2 with Java version 1.5 update 6. I was unable to replicate the segfault. I may have an explanation of the crash. Can you please try to do a 'dig -x a.b.c.d' on the Linux box, where a.b.c.d is the ip address of the Windows machine. What is the output? Are you thinking that it is crashing because there is no reverse lookup for the windows IP address? I confirmed that there is not a reverse lookup for this particular windows machine. I have the output below as well as additional O/S version info. dig -x 138.74.10.102 output: ; <<>> DiG 9.2.4 <<>> -x 138.74.10.102 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30025 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;102.10.74.138.in-addr.arpa. IN PTR ;; AUTHORITY SECTION: 74.138.in-addr.arpa. 3600 IN SOA ns1.snc.edu. postmaster.snc.edu. 2006032901 72001 1800 3628800 14400 ;; Query time: 1 msec ;; SERVER: 138.74.0.62#53(138.74.0.62) ;; WHEN: Thu Apr 20 13:24:15 2006 ;; MSG SIZE rcvd: 102 Debian Linux uname -a output: Linux favre 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC 2005 i686 GNU/Linux Windows Info: Windows XP Professional, Version 2002, Service Pack 2 Yep, that's it. It does a reverse lookup before it prints the "Connection from ..." message, but it doesn't handle the failure. It will be fixed for beta 3. Thanks for helping me debug this. Fixed on the trunk from rev. 1740. |