![]() ![]() Transaction based software configuration management (SCM) system. JOB: DirDiff has tkdiff 4.2 included, a single executable can be downloaded from here:.Also, YaDT supports Git and Mercurial repositories. diff and cvs utilities are embedded inside YaDT. YaDT is written in Tcl/Tk and wrapped in a single executable file with the help of sdx and tclkit. With YaDT you can compare and merge 2 and/or 3 files. It is another front-end for diff and in earlier versions diff3 utility. Eskil (see that page for a comparison from 2005).Were you instead looking for information on how one might implement diff in Tcl?.Binaries are available for Windows and macOS. ![]() Also supports SCCS, RCS, and CVS, and Subversion. That would help you find out which functions in your program are calling so you can set up watches to look at variables.TkDiff is a Tk based interface to the Unix diff command which provides highlighting of difference regions, side by side viewing of files, linked scrolling, random access to the difference regions, file merge, and online help. Those 0x080? addresses should be memory addresses in use by your program, so they should not be named ? if debugging symbols are on. When you compile your libraries and executables, make sure you use the -g switch to gcc or g++, which ever one gets used. Is the tcl program possibly using fork()?!ġ - nVidia has some newer drivers out for Linux, have you tried them yet?Ģ - your one error you posted says “Cannot access memory at address 0x2” that means memory pointed to at the third byte of RAM, which is definately not where any of your program’s data, or the driver’s data should be. If a pthread_join() is not performed on threads that are created as joinable, you can create memory leaks (stack problems I think).Ģ - there are some problems that I have heard of when attempting to use pthreads and fork at the same time, forget where exactly, but it should be somewhere in the pthread docs if I’m not mistaken. Do you by any chance remember where? Or have any suggestion on a place where I could possibly find some more info?ġ - by default, on Linux, new threads started by pthread_create() are joinable. You said you read about something similar before. It seems to me that just including causes the problem. I also tried to remove everything from pack_pt, leaving only the bare initialization, and I get the same problem. Note also that the order in which I call the "package require"s doesn’t matter in this respect. This without even creating and starting the object that uses threads. Then as soon as I click on the window opened by pack_gl, I get the segfault problem I described in the previous post. % g start # now the first app has started Let’s say pack_gl is the package using openGL and pack_pt is the one using pthreads: I do for example But, beside all this, my problem is that I can’t even initialize the package. My two applications run independently, but one of them is supposed to run a tcl command defined by the other. Program received signal SIGSEGV, Segmentation fault.Ġx409d4102 in glGetError () from /usr/lib/libGL.so.1Ġx40337788 in _nvsym17113 () from /usr/lib/libGL.so.1 same thing but creating two different interpretes in tcl: BAD!.pthread in one C app and openGL in another, but both called from tcl: BAD!.pthread and openGL in the same C app, but called from tcl: BAD!.My system is running Gnu-Linux RedHat 7.3 and I use the nvidia drivers version 3123.ĭoes anyone know if it is possible (and how) to combine multithreaded apps with openGL apps in tcl? ![]() If I load the package and at the same time use another package based on openGL (for example togl) I get segmentation fault. This package uses linux threads (pthreads). ![]()
0 Comments
Leave a Reply. |