On Wed, May 10, 2017 at 2:55 PM, Rony <[email protected]> wrote:
> Ok, what do you think then are possible causes for these crashes? How
> would one be ableshould one proceed to systematically debug this?
>
I gave you suggestions several emails ago that you have completely ignored.
Just pasting stack traces from the crash and trying to throw the problem
over the wall for someone else to solve is not a good approach to take. So
far, you've ignored all of my previous attempts to educate you on what is
going on. You need to show that you are making an effort and ask SPECIFIC
questions about things. I have given you rather extensive explanations
about garbage collection/uninit/etc. in the past, but you are showing no
sign that you actually bothered reading any of them.
Rick
Rick
>
> My problem currently is that I have no conception of the overall
> architecture (what would it be from a bird eye's view?), nor from the
> dynamics (what happens exactly at startup, when a Rexx instance gets
> created and when terminated, how do the garbage collector and uninit
> mechanism work - strategies, pre-/postconditions they apply?).
>
> Maybe this (interpreter documentation) is something the devlopers should
> start immediately while working on bugs/crashes, before adding any new
> functionalities to the interpreter?
>
> ---rony
>
> Rony G. Flatscher (mobil/e)
>
> Am 10.05.2017 um 19:41 schrieb Rick McGuire <[email protected]>:
>
> Sorry, I'm not interested in getting that involved with this again. I will
> answer specific questions about how the code works, but that's the limit. I
> will NOT get involved in directly debugging these issues.
>
> Rick
>
>
>
> On Wed, May 10, 2017 at 1:33 PM, Rony G. Flatscher <
> [email protected]> wrote:
>
>> Rick, would it help, if I created a zip-archive to download with
>> directions how to start the Rexx
>> application (using JavaFX)? If so, please let me know which bitness you
>> would need for the
>> bsf4oorexx.dll (pre-requisite is that you have Java 1.8 installed). Also,
>> I can make the 32- and
>> 64-debug versions of ooRexx (from today's trunk with your fix for the
>> memory leak applied)
>> available, either as an NSIS installer or as a zip-archive of the
>> bin-directories.
>>
>> This might allow you to better debug the cause with Visual Studio or the
>> like. It is strange that
>> this application causes different errors it seems, depending on the
>> bitness of the debug version of
>> ooRexx.
>>
>> ---rony
>>
>> P.S.: All other JavaFX samples work flawlessly with the patched version.
>>
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Oorexx-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
