You might know me as a stout supporter of CMake transition, but a single
experience shattered my certainity. Today i tried to resolve a backtrace for a
bug report, done with a cmake iso. The results were horrendous. The backtrace
was lenghty, but on rbuild such task would take around 15 mintues
LOL!
Nothing more to say.
After months you suddenly come up and notice that something doesn't work?
Awesome!
Keep it up people, we'll drop rbuild next year.
...
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ro
Sure, no problem. Just tell me how to debug explorer on msvc? Oh, no go?
Its up to you, developers. You can do all by yourself and dont need any
assistance from others, so why bother that some lousy frames will not be
traced? As you can expect that in most cases they wont be. Are you ok with tha
Irony is cool ;)
Seriously all Caemyr's points are valid. We can go to a better debug
format anytime, not specifically at the time of cmake switch.
WBR,
Aleksey.
On Oct 8, 2011, at 9:09 PM, cae...@myopera.com wrote:
Sure, no problem. Just tell me how to debug explorer on msvc? Oh,
no go?
Aleksey Bragin wrote:
Seriously all Caemyr's points are valid. We can go to a better debug
format anytime, not specifically at the time of cmake switch.
Then I hope that Amine's r54055 commit message was a bit ironic and
build doesn't really need twice the disk space with RSYM. Because in
th
Colin Finck wrote:
This process is fairly scriptable by the way and this has already been
done, see
http://svn.reactos.org/svn/reactos/trunk/tools/RosBE-Windows/Root/reladdr2line.cmd?revision=27678&view=markup
Correct link:
http://svn.reactos.org/svn/reactos/trunk/tools/RosBE-Windows/Root/rel
On 09/10/2011 13:44, Colin Finck wrote:
Then I hope that Amine's r54055 commit message was a bit ironic and
build doesn't really need twice the disk space with RSYM. Because in
this case, we get ourselves in another mess and the RAM-Disk on the
Debug slave will run out of space.
There was no
