Re: [Mingw-w64-public] winpthread build with static edition

2011-07-09 Thread Kai Tietz
Thanks, but a backtrace would be better (in gdb after break just type 'bt' and press enter. Anyway, I added a check here, which might be helpful, at revision 4263. It could fix your issue. Regards, Kai 2011/7/9 PcX xunxun1...@gmail.com 于 2011/7/9 13:05, PcX 写道: I tried to debug

Re: [Mingw-w64-public] winpthread build with static edition

2011-07-09 Thread PcX
2011/7/9 17:00, Kai Tietz : Thanks, but a backtrace would be better (in gdb after break just type 'bt' and press enter. Thanks. I type bt, and the out put: [New Thread 372.0x430] Program received signal SIGSEGV, Segmentation fault.

Re: [Mingw-w64-public] winpthread build with static edition

2011-07-09 Thread PcX
2011/7/9 17:50, PcX : then all work well. I fix my result. It can run, but seem to enter an endless loop. -- Best Regards, PcX -- All of the data generated in your IT

Re: [Mingw-w64-public] winpthread build with static edition

2011-07-09 Thread PcX
2011/7/9 17:59, PcX : 2011/7/9 17:50, PcX : then all work well. I fix my result. It can run, but seem to enter an endless loop. -- Best Regards, PcX This is more information: -- Best

Re: [Mingw-w64-public] winpthread build with static edition

2011-07-09 Thread Kai Tietz
So, this backtrace was indeed interesting. Thanks for telling me my typo ... it should be indeed IsBadReadPtr. So I added a possible fix here in sem.c at revision 4265 for this. It is to be expected that you get in debugger still an exeption (as notice not a segfault itself). This is caused by

Re: [Mingw-w64-public] winpthread build with static edition

2011-07-09 Thread PcX
2011/7/9 18:36, Kai Tietz : The potential fix for this is at rev 4265. I update to 4265, but it also has the problem: -- Best Regards, PcX -- All of the data generated in your

Re: [Mingw-w64-public] winpthread build with static edition

2011-07-09 Thread PcX
2011/7/9 19:15, PcX : 2011/7/9 18:36, Kai Tietz : The potential fix for this is at rev 4265. I update to 4265, but it also has the problem: -- Best Regards, PcX This is more information: -- Best

[Mingw-w64-public] Building GCC with my scripts under MSYS

2011-07-09 Thread Ruben Van Boxem
In an attempt to help all these people trying to build GCC toolchains (for reasons still very mysterious to me), I attempted modifying them to build a 32-bit to 64-bit cross-compiler and tried running it on MSYS with my 32-bit toolchain. In the gcc-c stage, I get this error: make[1]: Entering

Re: [Mingw-w64-public] Building GCC with my scripts under MSYS

2011-07-09 Thread Earnie
JonY wrote: On 7/10/2011 01:55, Ruben Van Boxem wrote: In an attempt to help all these people trying to build GCC toolchains (for reasons still very mysterious to me), I attempted modifying them to build a 32-bit to 64-bit cross-compiler and tried running it on MSYS with my 32-bit toolchain.

Re: [Mingw-w64-public] Building GCC with my scripts under MSYS

2011-07-09 Thread PcX
于 2011/7/10 1:55, Ruben Van Boxem 写道: Which is very odd, because the file that does not exist, exists. Sometimes, on msys, if your source directory and build directory is different, the some file does not exit error will appear. I don't know this reason. So if I build gcc on msys, I will build