Re: latest build 5.5 build 1162 problems & questions

[Arnold W. <awi...@te...>]

Salvador Eduardo Tropea wrote:
> [snip]
> 
> That's a very strange calling sequence.
> It looks like the debug info isn't enough because you didn't get source 
> file and line number information. But at least you got the function names.
> The CLY_YieldProcessor() call (calling usleep and nanosleep) looks like 
> the "idle" loop when the library is waiting for input.
> The strange part is that it seems to be called from execDialog() ... I 
> tried to reproduce such an interruption and I got "TSetEditorApp::idle" 
> there. So I think you are mixing binaries. The TV calls seems to be OK, 
> but the functions inside the editor doesn't have much sense.
> Please double check you are running a copy with debug info. Also check 
> that all the editor was recompiled when you selected the debug info. 
> This traceback is showing "execDialog" for two addresses quite different.
> The other strange thing is that this traceback is too small, doesn't 
> look like a traceback of the editor loading the desktop file.

I have done in both tvision first and then setedit:

'make clean'
./configure --debug
make

then in setedit
make install

I still get the same behavior. When I have no tcedit.dst file, it hangs. 
If I copy an old one or rename an old dst file to tcedit.dst it runs and 
tells me it is build 1162.

When I run it under ddd, it also tells me there is no debug info - so 
now I'm confused.

If I run the program in makes i.e.
cd makes
editor.exe -d 3

it also hangs, but when I kill it from another window, I do get the gdb 
window and can do a backtrace, but I have not been able to cut & paste 
again from that window - I know I did it last week - but this week a 
thick "fog" has descended and I can't get it to work.

I rebooted and even as root I cannot cut-n-paste.

One thing, though, it does look different, but too much to accurately 
type by hand.

Arnold