|
That makes sense. xt5250 launches a new window to open tn5250 -- so you're getting the (previously reported) segmentation fault in the new window, and then the program ends (causing the window to close.) Unfortunately, that doesn't tell us what the problem is. Please try running with the trace parameter enabled. For example: tn5250 trace=/path/to/trace.txt your-hostname Then, post the contents of trace.txt. Possibly it'll give us some insight into the problem? If not, we'll need a MacOS programmer who can reproduce and debug your problem. Judging by the lack of responses to your original message, I suspect that we don't have any MacOS programmers monitoring the list? On 6/15/2012 1:37 PM, Hugh Caley wrote:Here's the output of trace:>I have also tried it using the xt5250 wraparound script (and X11, of
>course). I get a window for a moment and then it's gone.
>
>Hugh
Non-Blocking
tn5250_dbuffer_clear_table() entered.
tn5250_char_map_new: map = "37"
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.