jrodrigo has contributed to 8 posts out of 18238 total posts
(0.04%) in 943 days (0.01 posts per day).
20 Most recent posts:
I'm starting to think that this comes from a long running wineserver...
I cannot force the dumps under a fresh wineserver.
I will restart a fresh wineserver with iqconnect each time and monitor this dumps for some hours/days,
we'll see if it is a wineserver issue.
The only files that I have under Docs are:
Keep in mind that this crash is happening launching and closing iqconnect.exe, it is not a crash on operation. Could be cleanup or initializing issues.
Should I activate something on the iqconnect?
BTW I have totally restricted the wine debugger, so no crash notifier popup comes up nor the debugger kicks in, it justs crashes;
in this way I can get to restart iqconnect daemon style if a crash happens during operation.
Well after starting and stopping iqconnect.exe beta for a good number of times during a 12 hour period I have some not so random crashes.
It seems to always follow a similar path through _XlcDestroyLocaleDataBase (some times RtlRaiseException is on the stack too):
=>0 0xffffe430 __kernel_vsyscall+0x10() in [vdso].so (0x0152b7f8)
1 0xf73e7f47 gsignal+0x46() in libc.so.6 (0x0152b7f8)
2 0xf73e9616 abort+0x155() in libc.so.6 (0x0152b7f8)
3 0xf7425e72 in libc.so.6 (+0x6be71) (0x0152b7f8)
4 0xf742ba5a in libc.so.6 (+0x71a59) (0x7d9df1e8)
5 0xf742c6a8 in libc.so.6 (+0x726a7) (0x7d9df1e8)
6 0x7de700d4 _XlcDestroyLocaleDataBase+0x83() in libx11.so.6 (0x7d9be9c0)
7 0x7de74cb0 in libx11.so.6 (+0x4ecaf) (0x7dd10008)
8 0x7de7c4b6 _XCloseLC+0x75() in libx11.so.6 (0x7dd10008)
9 0x7de7c500 _XlcCurrentLC+0x2f() in libx11.so.6 (0x7dd10008)
10 0x7de752ed _Xlcmbstowcs+0xdc() in libx11.so.6 (0x7dd10008)
11 0x7de753d3 _Xmbstowcs+0x32() in libx11.so.6 (0x7dd10008)
12 0x7de8a86e in libx11.so.6 (+0x6486d) (0x7dd10008)
13 0x7de889c6 _XimLocalOpenIM+0x3f5() in libx11.so.6 (0x7da06360)
14 0x7de86e57 _XimOpenIM+0xf6() in libx11.so.6 (0x7da06360)
15 0x7de6c837 XOpenIM+0x46() in libx11.so.6 (0x0152dff8)
16 0x7dff0247 in winex11 (+0x50246) (0x0152dff8)
17 0x7dff1461 in winex11 (+0x51460) (0x0152e028)
18 0x7dfed783 in winex11 (+0x4d782) (0x0152e0e8)
19 0x7dfe61e1 X11DRV_WindowPosChanging+0x320() in winex11 (0x0152e178)
20 0x7eb6105f in user32 (+0xa105e) (0x0152e2c8)
21 0x7eb5cab9 in user32 (+0x9cab8) (0x0152e488)
22 0x7eb5642f CreateWindowExA+0x18e() in user32 (0x0152e718)
23 0x1023255c in mfc110 (+0x23255b) (0x0152e784)
24 0x1022d058 in mfc110 (+0x22d057) (0x0152e7f0)
25 0x1021b05a in mfc110 (+0x21b059) (0x0152e848)
26 0x1021b2f8 in mfc110 (+0x21b2f7) (0x0152e860)
27 0x1021a9dc in mfc110 (+0x21a9db) (0x0152e87c)
28 0x0040a8fd in iqconnect (+0xa8fc) (0x004acc34)
29 0x00613c98 (0x00613cc0)
0xffffe430 __kernel_vsyscall+0x10 in [vdso].so: popl %ebp
Could be a wine issue or maybe something going unhandled it is hard to tell. I leave you a log file with multiple occurences.
By the way I'm starting wine in X11 synchronous mode:
I continue to run the beta version and I can confirm that the the connection dialog pops up some times
and we are back to the 'procedural CONNECT impossibility' bug, human action is required (ie: click on the connect button).
I've run some more tests with the Diagnostics tool.
First of all, running the full test suite the application crashes.
I've read on the forum that this is due to the COM interfacing that is going to be removed.
There is some strange behaviour when launching the Diagnostic's traceroute.
I have activated the raw sockets capability for wine, so the Diagnostic's ping test works ok.
But the traceroute test reports Error:11010 (+very long timeout) for all the intermediate hops,
only the last hop returns the timing info.
Tracerouting the same boxes with the native Linux traceroute tool yields a lot more information,
the native tool manages to get timing info for some of the first hops (and some times the last one).
If this tracerouting capability is used by the iqconnect.exe application itself this behaviour could be bad.
In addition I would like to know if you are planning any more beta releases (maybe fixing the CONNECT issue),
because this beta seems to work better under wine.
The random crashes on iqconnect.exe start and shutdown under wine seem to have disappeared.
I knew that those crashes were related to the wine - iqconnect.exe interaction and it is nice that they are gone.
I would like to continue using the beta on a daily basis but the CONNECT problem impedes me to do so.
I have to install different iqconnect versions back and forth.
Thanks again Tim.
Having a native Linux version of iqconnect in console mode would be very nice.
Only the bare bones, maybe a static 64 bits release.
That could be very nice indeed.
I've run some tests with the beta 18.104.22.168 and it does not connect after issuing:
It simply does nothing, if I click the connect button it connects OK.
Under the 22.214.171.124 version it works as expected, I issue AUTOCONNECT OFF and then CONNECT and it works, no problem.
The beta 126.96.36.199 seems to reconnect when I issue CONNECT after a network loss.
It is only the first time after launching the client that CONNECT does not work???
I'm requesting the 5.1 protocol by the way. Here is the the input from the client:
S,REGISTER CLIENT APP COMPLETED,\n
S,LOGIN INFO SAVED,\n
Issuing multiple CONNECT and never connects.
Using wine under Linux:
Edited by jrodrigo on Jan 28, 2016 at 04:40 PM
The 188.8.131.52 version hangs while logging on "Retrieving IP information" under wine.
It was a temporary problem (from time to time), but today 25/04/2015 at 9:30 EST
it has become constant, it is impossible to get logged so I have downgraded to
the 184.108.40.206 stable version.
The stable 220.127.116.11 did work as expected, I have not encountered this problem or
any other with this version.
I have attached the captured window with the client stucked while logging.