digitalmars.D.bugs - Assertion failure: '0' on line 64 in file 'tocvdebug.c'
- Ant (5/5) Oct 28 2004 dmd 0.104, windows XP
- Walter (4/8) Oct 28 2004 Please send in the example so I can fix it! (It "worked" on 0.102 becaus...
- Ant (13/15) Oct 28 2004 here it is:
- Regan Heath (7/8) Oct 28 2004 Indeed, without the 'input' you don't really know what the problem was.
- Walter (7/12) Oct 29 2004 Thanks for the example.
dmd 0.104, windows XP now I get this: Assertion failure: '0' on line 64 in file 'tocvdebug.c' it was OK on 102 Ant
Oct 28 2004
"Ant" <Ant_member pathlink.com> wrote in message news:clrtd1$qqm$1 digitaldaemon.com...dmd 0.104, windows XP now I get this: Assertion failure: '0' on line 64 in file 'tocvdebug.c' it was OK on 102Please send in the example so I can fix it! (It "worked" on 0.102 because 0.102 didn't attempt to output cv debug info for a lot of types.)
Oct 28 2004
In article <cls4k7$12l6$3 digitaldaemon.com>, Walter says...Please send in the example so I can fix it! (It "worked" on 0.102 because 0.102 didn't attempt to output cv debug info for a lot of types.)here it is: class A { unittest { } } dmd -c -g Bug.d Assertion failure: '0' on line 64 in file 'tocvdebug.c' Ant (See now how completly useless the assert information is?)
Oct 28 2004
On Fri, 29 Oct 2004 02:02:28 +0000 (UTC), Ant <Ant_member pathlink.com> wrote:(See now how completly useless the assert information is?)Indeed, without the 'input' you don't really know what the problem was. Only a good stack trace will really tell you. Regan -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Oct 28 2004
"Ant" <Ant_member pathlink.com> wrote in message news:cls8bk$16j5$1 digitaldaemon.com...In article <cls4k7$12l6$3 digitaldaemon.com>, Walter says... dmd -c -g Bug.d Assertion failure: '0' on line 64 in file 'tocvdebug.c' Ant (See now how completly useless the assert information is?)Thanks for the example. A compiler is pretty complicated. Without the example that drives the compiler, it's just a huge waste of time trying to guess the path it took to get there. A stack trace doesn't give that information either, but if I need one, I just load it into the debugger.
Oct 29 2004