Re: distcc & gdb

> Is this FAQ item still true ?

It shouldn't be true if you are using pump mode and ELF binaries.  Distcc
post-processes the object files to fix up the source references.

As a workaround you can use the gdb directory command.

Otherwise you'll need to debug it...

Verify that it is due to distcc by running distccd locally and using your
hostname or IP on DISTCC_HOSTS (with ,cpp,lzo) - that ensures that you're
running the "remote" compiles on same host with same compiler.

Then try objdump -A --disassemble on object file and diff against object
file built locally.
On Thu, May 3, 2012 at 3:33 PM, Stéphane Vandenbogaerde <[email protected]>wrote:

> Le 30/04/2012 16:42, Fergus Henderson a écrit :
>
>
>  Try using pump mode.
>>
>> Which architecture are you compiling for?
>>
>
> I do use pump.
>
> My workstation and the distcc server are on CentOS 6.2 and use gcc 4.5.3.
>
> I opened with vim the compiled file put by distcc on my workstation, and
> searched the source path. It is the original path.
> So that should be OK. But it isn't : I can't stop at my breakpoints when
> debugging.
>
> Note that I try to put the breakpoint in a dynamic library (compiled
> through distcc).
>
> No problem if I compile locally.
>



-- 
Fergus Henderson <[email protected]>

"Defend the user, exclude no one, and create magic." -- Eric Schmidt.

__
distcc mailing list            http://distcc.samba.org/
To unsubscribe or change options:
https://lists.samba.org/mailman/listinfo/distcc