[bcp] Bcp namespace rename on 1.44 release beta 1 causes runtime errors on range lib and build tool
John (and others), I just tested a full Boost extract with namespace rename (and namespace alias) on 1.44 release beta 1. After bootstrap building bjam from the distribution, I built bcp and then attempted to extract all of Boost (libs and tools) with namespace rename and alias (this time using "." to extract everything). I'm getting runtime errors from bcp: **** exception(200): Invalid parameter detected by C runtime library I've isolated it down to one library and one tool - the range library, and the build tool. All other libraries and tools individually successfully extract (with namespace rename). I tried doing a Boost root library build (with bjam) after the extract, but missing critical pieces of build is causing problems (which makes sense). I assume this is a high pri (at least the build tools part), so I'll be happy to help in any way. Cliff
I just tested a full Boost extract with namespace rename (and namespace alias) on 1.44 release beta 1.
After bootstrap building bjam from the distribution, I built bcp and then attempted to extract all of Boost (libs and tools) with namespace rename and alias (this time using "." to extract everything).
I'm getting runtime errors from bcp:
**** exception(200): Invalid parameter detected by C runtime library
Which compiler? Works OK for me here with VC9 and building in release mode (note the debug builds can sometimes stack overflow - but fixing that requires a much more complex re-write than we can do for this release). John.
From: "John Maddock" <boost.regex@virgin.net>
After bootstrap building bjam from the distribution, I built bcp and then attempted to extract all of Boost (libs and tools) with namespace rename and alias (this time using "." to extract everything).
I'm getting runtime errors from bcp:
**** exception(200): Invalid parameter detected by C runtime library
Which compiler? Works OK for me here with VC9 and building in release mode (note the debug builds can sometimes stack overflow - but fixing that requires a much more complex re-write than we can do for this release).
Sorry - I should have included compiler info. This was with VS2005 (VC8). I will also be testing with g++ 4.1.2, but haven't had a chance yet. Actually, if it works with g++, or I successfully perform the extract / namespace rename with VC9, that's satisfactory for my work project needs (with 1.44 final release, of course). But it's probably worthwhile tracking down my failures, for other potential users, and general robustness. Do you want to perform some deeper analysis of the problem? Cliff
Which compiler? Works OK for me here with VC9 and building in release mode (note the debug builds can sometimes stack overflow - but fixing that requires a much more complex re-write than we can do for this release).
Sorry - I should have included compiler info. This was with VS2005 (VC8). I will also be testing with g++ 4.1.2, but haven't had a chance yet.
Actually, if it works with g++, or I successfully perform the extract / namespace rename with VC9, that's satisfactory for my work project needs (with 1.44 final release, of course). But it's probably worthwhile tracking down my failures, for other potential users, and general robustness.
Do you want to perform some deeper analysis of the problem?
OK, I've tracked this down to a zero-byte file lurking inside Boost.Range somewhere. The issue that causes bcp to choke on this had already been fixed in Trunk, but not merged to Release (my fault). John.
From: "John Maddock" <boost.regex@virgin.net>
Do you want to perform some deeper analysis of the problem?
OK, I've tracked this down to a zero-byte file lurking inside Boost.Range somewhere. The issue that causes bcp to choke on this had already been fixed in Trunk, but not merged to Release (my fault).
Thanks, again, John! I meant to say (earlier): "Do you want _me_ to perform some deeper analysis of the problem?" - hope no offense was taken. If you get permission to merge, I'll test again as soon as there's another release beta ready. I don't know how the release schedule is going, but it would be great if I get a chance to do deeper testing after the extraction / namespace rename (i.e. run tests on many of the libraries). Cliff
participants (2)
-
Cliff Green -
John Maddock