summaryrefslogtreecommitdiffstats
path: root/BUGS
blob: 98f495db4c49eeada8c78310de66b7509f8fe7c6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Known issues
------------
1. Error messages are not transmitted from the previous instance of KDocker to
the latest instance. So, if you already have KDocker running and you start
another instance of KDocker saying "kdocker blah", you wont receive any error
message.

2. Problem with relative paths if new instance of KDocker and old instance of
KDocker 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 kdocker.pro (in fact just uncomment it)
	DEFINES += ENABLE_TRACING
* Now do a "make clean" and "then make".
* Launch KDocker. Recreate the problem.
- Right Click on the tray icon.
- Choose "About KDocker"
- 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 KDocker process, it will dump all the trace to
  ~/kdocker.trace. Send that file to me.

May the force be with you.