Distcc and debugging in kdevelop
ghost at cs.msu.su
Wed May 3 12:50:56 BST 2006
On Wednesday 03 May 2006 13:46, Johan Maes wrote:
> When I compile my application locally, I can perfectly debug it.
> When I use distcc to compile it, then for all the files compiled on the
> remote machine, kdevelop will not be able to find the source.
> If I put a breakpoint in motion.cpp at line 544, then gdb will stop the
> program when the breakpoint is hit, but KDevelop will say: No source: 544
> in motion.cpp.
> Any ideas?
I would suppose that gdb or gcc is buggy ;-) Really, can you get gdb to
produce the right source file name in the console? If not, then the only
solution on KDevelop side is to pop up a dialog box saying "have no idea
where's this file, specify directory locally".
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
More information about the KDevelop