On 6/16/2013 12:44 PM, Chris Morgan wrote:
Hi Wayne.
I think the difference may be due to where the app was started. It's
the same build with debug enabled and installed from the kicad testing
repository. The actual directories are odd though, they are off of a
backed up root install from
On Mon, Jun 17, 2013 at 11:11 AM, Wayne Stambaugh stambau...@verizon.netwrote:
On 6/16/2013 12:44 PM, Chris Morgan wrote:
Hi Wayne.
I think the difference may be due to where the app was started. It's
the same build with debug enabled and installed from the kicad testing
repository.
On 6/17/2013 6:19 AM, Chris Morgan wrote:
It looks like I won't be able to test the fix here. The
flag, /wxDIR_NO_FOLLOW/, appears to have been added in wxWidgets 2.9.5
according to the documentation.
On 06/17/2013 11:34 AM, Wayne Stambaugh wrote:
On 6/17/2013 6:19 AM, Chris Morgan wrote:
It looks like I won't be able to test the fix here. The
flag, /wxDIR_NO_FOLLOW/, appears to have been added in wxWidgets 2.9.5
according to the documentation.
On 6/16/2013 12:44 PM, Chris Morgan wrote:
Hi Wayne.
I think the difference may be due to where the app was started. It's
the same build with debug enabled and installed from the kicad testing
repository. The actual directories are odd though, they are off of a
backed up root install from
On 6/17/2013 2:10 PM, Dick Hollenbeck wrote:
On 06/17/2013 11:34 AM, Wayne Stambaugh wrote:
On 6/17/2013 6:19 AM, Chris Morgan wrote:
It looks like I won't be able to test the fix here. The
flag, /wxDIR_NO_FOLLOW/, appears to have been added in wxWidgets 2.9.5
according to the documentation.
On 6/15/2013 8:12 PM, Chris Morgan wrote:
Dick turned out to be correct, that was some good insight there.
Attached strace to the process and sure enough it is traversing a
directory that has symlinks, several of which appear to be pointing back
to the same directory. So, the process is making
Hi Wayne.
I think the difference may be due to where the app was started. It's
the same build with debug enabled and installed from the kicad testing
repository. The actual directories are odd though, they are off of a
backed up root install from another server and are symlinks that
aren't
Oh that flag is allowed for the getallfiles call. I would have tried
that if I had noticed that. Ill give it a shot tonight but I bet that
will fix it. Whether it is the right thing to do is another thing.
Chris
On Jun 16, 2013, at 11:25 AM, Wayne Stambaugh stambau...@verizon.net wrote:
On
Hello.
I'm seeing a pcbnew hang at 100% cpu, but only if I run it via the kicad
window. If I start pcbnew from a console window it runs fine. This is with
a few day old kicad-testing branch, Kubuntu 13.04 64bit.
Here is the stack trace:
gdb) bt
#0 0x7f7b6a75 in __xstat64 () from
No idea. This is new code.
KISYSMOD env var is not used yet, so one option is to comment out the entire
block from
194 to 213.
But I think Wayne would appreciate getting help nailing the problem. You can
try and log
the execution with fprintf(). Using printf() likely won't work, since the
Ok. Ill see what I can come up with. Good idea on the recursive
symlink. Surprised wx wouldn't handle that situation.
Ill try to figure it out this evening.
Chris
On Jun 15, 2013, at 5:31 PM, Dick Hollenbeck d...@softplc.com wrote:
No idea. This is new code.
KISYSMOD env var is not used
Dick turned out to be correct, that was some good insight there.
Attached strace to the process and sure enough it is traversing a directory
that has symlinks, several of which appear to be pointing back to the same
directory. So, the process is making progress but because of the several
symlink
13 matches
Mail list logo
