On Thu, 17 Dec 2009, Bill Evans wrote:

So, I tried version 0.17.4 and that problem appears to have been fixed.
However, there's a bug in 0.17.4 that causes a run time error when
clicking on the last line of the 5250 window. The error occurs even
before signing on to the host.

I generated a trace file and the run time error occurs here:

Assertion (This)->cy < (This)->h failed at ../lib5250/dbuffer.c, line 412.
I looked at the code in dbuffer.c on the website. Routine
tn5250_dbuffer_cursor_set in module dbuffer.c triggers the ASSERT_VALID
macro. If line 24 is clicked on, the ASSERT_VALID macro will fail since
at that point (This)->cy < (This)->h cannot be true since line 24 cannot
be less than 24, the screen height.

Can't this be easily resolved by recompling with NDBUG defined on the
command line with the -D option to disable the ASSERT macros?
Unfortunately, I don't have the facilities to perform a re-compilation.

Could someone help with this? I need the clipboard copy/paste fixes in
this version but I cannot cope with it terminating when I accidentally
click on line 24.

Hi Bill,

I read your message but I don't have the tools to do anything about it. I don't have windows compilers or even a windows machine. Scott wrote the windows front end so hopefully he finds time to post here, though he is very busy.

I don't think disabling ASSERT is the right way to go. The ASSERT macros are there to catch errors, disabling them will simply cause the error to continue. Are you saying that the problem lies in the ASSERT code itself?

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].