Hello Martin.
> Maybe that mail got lost?
Huh, witch one ?
> You never give up! ;-)
Yes, when I find a solution ;-)
> How
> looks the stack trace at the crash?
Not easy to give trace of the crash of meseide when show main.pas as form
(because the debugger crash with mseide crash)...
So I c
On Saturday 05 August 2017 15:22:02 Fred van Stappen wrote:
> Hello Martin.
>
> > Maybe that mail got lost?
>
> Huh, witch one ?
>
> > You never give up! ;-)
>
> Yes, when I find a solution ;-)
>
> > How
> > looks the stack trace at the crash?
>
> Not easy to give trace of the crash of meseide when
Hello Martin.
Here how I did:
1) Change code in msegui.pas, as described in previous mail and recompile
meseide to be able to load noisegen.pas
2) When noisegen.pas is loaded, compile it using this debug code:
> debugging line 8268 of msegui.pas with this (code corrected = no crash)
wam_c
> This is not the thread which throws the exception. Please click in thread
> window in the different rows until the stack window shows the exception or
> signal.
#0 2774 unknown "noisegen" pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:143
---
On Saturday 05 August 2017 17:30:12 Fred van Stappen wrote:
>
> ---> crash ---> here Stack result:
>
[...]
> #17 0043E802 msegui.pas:9527 CLIENTRECTCHANGED(this=0x77f99290)
> #18 0068B301 msedispwidgets.pas:515 CLIENTRECTCHANGED(this=0x77f99290)
> #19 004301F1 msegui.pas:4804 UPD
5 matches
Mail list logo