freebsd - gdb can't find any source after compile through distcc -


i'm using several freebsd machines, , of them in same version,

10.3-release i386. , installed distcc every machine through ports,

/usr/ports/devel/distcc/.

i think distcc version distcc-3.1 because of distcc-3.1.tar.bz2 file in /usr/ports/distfiles/.

any compile done successfully, in fast way expected.

but after try make break point in gdb, cannot catch source files of project.

it may result of temp file such 'distccd_xxxxxx.ii' distcc / distccd give , receive between machines.

i've tried 'directory' command in gdb, , not sufficient because file tree complicated , big.

gdb fine when compiled locally without distcc.

is there solutions break situation?

have seen entry in distcc faq? https://github.com/marksatt/distcc/blob/master/doc/web/faq.html :

unfortunately caused bug in gcc, hope fixed in future release. gcc embeds directory compiler (cc1) run, when ought record directory source came from.

can work around using "directory" command in gdb tell find source, or passing absolute file name when compiling.

tim janik has unofficial patch distcc works around think won't merge because it's better fix in gcc.

debian #148957.

there discussion bug on gcc-patches mailing list.
can affect other programs rely on debug stabs, such addr2line, , results in object files not being byte-for-byte identical when include source directory. same bug affects ccache.

the patch seems here: http://testbit.eu/~timj/patches/


-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more