|
|
|
|
Known issues
|
|
|
|
|
------------
|
|
|
|
|
1. Error messages are not transmitted from the previous instance of TDEDocker to
|
|
|
|
|
the latest instance. So, if you already have TDEDocker running and you start
|
|
|
|
|
another instance of TDEDocker saying "tdedocker blah", you wont receive any error
|
|
|
|
|
message.
|
|
|
|
|
|
|
|
|
|
2. Problem with relative paths if new instance of TDEDocker and old instance of
|
|
|
|
|
TDEDocker are started from different directories (the current directory
|
|
|
|
|
information is not transmitted across instances)
|
|
|
|
|
|
|
|
|
|
Reporting Bugs
|
|
|
|
|
--------------
|
|
|
|
|
Bugs and wishes to gramakri at uiuc dot edu. Follow the guidelines below , if
|
|
|
|
|
possible and send it to me at gramakri at uiuc dot edu.
|
|
|
|
|
|
|
|
|
|
* Add the following line in tdedocker.pro (in fact just uncomment it)
|
|
|
|
|
DEFINES += ENABLE_TRACING
|
|
|
|
|
* Now do a "make clean" and "then make".
|
|
|
|
|
* Launch TDEDocker. Recreate the problem.
|
|
|
|
|
- Right Click on the tray icon.
|
|
|
|
|
- Choose "About TDEDocker"
|
|
|
|
|
- You should see a button called "Show Trace". Please note that this button
|
|
|
|
|
will appear only when compiled with tracing
|
|
|
|
|
- If you send SIGUSR1 to the TDEDocker process, it will dump all the trace to
|
|
|
|
|
~/tdedocker.trace. Send that file to me.
|
|
|
|
|
|
|
|
|
|
May the force be with you.
|
|
|
|
|
|
