What does this mean please?
in [Visual Objects]
|
From: Jamal on 26 May 2007 11:14 Goeff, It's very clear that is a VO compiler error but he's STILL using 2735!!! Which is better tell him the cause of error, which I can't guess the true reason for it, or wait for a wait for a fix for that old version, or just update to 2.8? Which the shotest route to the fix? VO 2.8 is very stable everyone without any service packs, much more stable than any previous version of VO. So why wait? Jamal "Geoff Schaller" <geoff_(a)software_objectives.com.au> wrote in message news:465787c6$1(a)dnews.tpgi.com.au... > Martin. > > I think you can ignore Jamal's insipid response, although I too would > recommend you upgrade to 2.8 at some stage. Perhaps after the first > service pack... <g> > > The error message here is caused by one of two things (because you still > get in them 2.8 <g>). Either one of the linked libraries has an > un-compiled entity within it or there is a corruption in the repo. > > Check all libs that they are all compiled and if that is not the cause, > reindex the repo, touch all and rebuild. > > Geoff > > > > "Martin" <spamspam(a)spam.spam> wrote in message > news:f370or$93g$1$8302bc10(a)news.demon.co.uk: > >> Date/Time: 2007-05-25 15:51:40 >> Version : Visual Objects 2.7b build 2735 >> >> Error : An unhandled exception (0xC0000005) occurred inside module: >> : C:\CAVO27\Bin\CAVOLINK.DLL at 0x1058F549 >> >> Registers: EAX = 0x939CDC2C EBX = 0x939CDC2C ECX = 0xDC47373C EDX = >> 0x00000018 >> : ESI = 0x24F19230 EDI = 0xDC47373C ESP = 0x0012E084 EBP = >> 0x0012E084 >
From: Geoff Schaller on 26 May 2007 21:20 Jamal, > It's very clear that is a VO compiler error but he's STILL using 2735!!! > Which is better tell him the cause of error, which I can't guess the true Perhaps if you read the question you might not appear so trite. You could answer the question if you really want to and then advise him to upgrade without appearing so sanctimonious. Yes he should upgrade but you can still advise him the cause of that error because it is well known and often discussed. > reason for it, or wait for a wait for a fix for that old version, or just > update to 2.8? Which the shotest route to the fix? Ah! But in this case, this particular bug IS NOT fixed in 2.8 - I have posted the exact bug that I get routinely in 2.8 as of now. Build 2816. > VO 2.8 is very stable everyone without any service packs, much more stable > than any previous version of VO. So why wait? Jamal, 2.7 is stable too so there is no rush to get 2.8. Build 2816 still contains some significant annoyances that seem mainly related to the help file somehow. I still routinely have to reindex the repo after importing 2.7 aefs and it is totally annoying that VO crashes on exit and after using and closing the help window. How can anyone put up with VO just shutting down without warning. Do you understand the corruptions that are possible with SCC sitting behind arbitrary shutdowns. Hence I am anticipating a quick patch (or the next build) and advise others to hold off a few days until this patch is released. There are also some annoyances with SCC I am running into. When I make a module local I am finding that I am unable to delete entities from the IDE. It seems to think the module is still under source control. Equally I can't rename them. I have to delete them and re-import them, rename them and then add them back to source control and then make them local again. Hard to do when disconnected from my SCC server. I am hoping that the vast resources of the VOPS crowd has come across these problems and notated them to Robert. Geoff
From: Jamal on 27 May 2007 00:00 >Ah! But in this case, this particular bug IS NOT fixed in 2.8 - I have >posted the exact bug that I get routinely in 2.8 as of now. Build 2816. Come on!! Exact bug with same register values, etc? Can't be!! Yes, it's a linker error but not the "Exact" bug! If Martin moves to VO 2.8 2816, he may or may not get the error. Don't expect Robert to fix a linker error reported 2735!! <vbg> If he get the same error and sends the report to Grafx, I am sure it will get fixed soon. I did not have the same problem with the Help file. Did you report you issue to Grafx? You're using 2816 and you want other to hold off based on your own experience, however, many other developers say it's the best version of VO based on their extensive testing and use. Martin and other can utilize the the current version and get a head start to clean up their applications until next patch. Jamal "Geoff Schaller" <geoff_(a)software_objectives.com.au> wrote in message news:4658dcf0$1(a)dnews.tpgi.com.au... > Jamal, > >> It's very clear that is a VO compiler error but he's STILL using 2735!!! >> Which is better tell him the cause of error, which I can't guess the true > > Perhaps if you read the question you might not appear so trite. You could > answer the question if you really want to and then advise him to upgrade > without appearing so sanctimonious. Yes he should upgrade but you can > still advise him the cause of that error because it is well known and > often discussed. > >> reason for it, or wait for a wait for a fix for that old version, or >> just >> update to 2.8? Which the shotest route to the fix? > > Ah! But in this case, this particular bug IS NOT fixed in 2.8 - I have > posted the exact bug that I get routinely in 2.8 as of now. Build 2816. > >> VO 2.8 is very stable everyone without any service packs, much more >> stable >> than any previous version of VO. So why wait? > > Jamal, 2.7 is stable too so there is no rush to get 2.8. Build 2816 still > contains some significant annoyances that seem mainly related to the help > file somehow. I still routinely have to reindex the repo after importing > 2.7 aefs and it is totally annoying that VO crashes on exit and after > using and closing the help window. How can anyone put up with VO just > shutting down without warning. Do you understand the corruptions that are > possible with SCC sitting behind arbitrary shutdowns. > > Hence I am anticipating a quick patch (or the next build) and advise > others to hold off a few days until this patch is released. > > There are also some annoyances with SCC I am running into. When I make a > module local I am finding that I am unable to delete entities from the > IDE. It seems to think the module is still under source control. Equally I > can't rename them. I have to delete them and re-import them, rename them > and then add them back to source control and then make them local again. > Hard to do when disconnected from my SCC server. I am hoping that the vast > resources of the VOPS crowd has come across these problems and notated > them to Robert. > > Geoff > >
From: Geoff Schaller on 27 May 2007 00:42 Jamal, > Come on!! Exact bug with same register values, etc? Can't be!! > Yes, it's a linker error but not the "Exact" bug! If Martin moves to VO 2.8 It has the same exception handler code of 0xC0000005 so it is the same bug caused the same way. I have posted my error log entry so that Robert can extract the relevant info. > Don't expect Robert to fix a linker error reported 2735!! <vbg> You see, he didn't. He just asked what it meant and fortunately the meaning is quite clear and steps to avoid it equally clear. > I did not have the same problem with the Help file. Did you report you issue > to Grafx? Quite a few people are experiencing this. It has been mentioned often enough. > You're using 2816 and you want other to hold off based on your own > experience, however, many other developers say it's the best version of VO Now you are reading too much into what I said. No I am not 'using' 2.8 commercially yet. I have to rebuild a GSR and project builder now that VOPP 3.1 is denied me. I am working with 2.8 like I work with Microsoft beta products. I have not rebuilt my commercial apps in 2.8 because they are going to need extensive testing. There are so many GUI class changes that everyone should be really cautious before they release their code. I have toolbar, menu, controlnotify and splitwindow issues I need to resolve before I can risk my apps on clients. I am working through this and resolving issues as I go. There are important problems here and obviously some important fixes to come out from GrafX very soon. I recommend folks holding off until they see those fixes or they'll go through what I have. Geoff
From: Robert van der Hulst on 27 May 2007 04:39 Hi Geoff, On Sun, 27 May 2007, at 04:42:17 [GMT +0000] (which was 6:42 where I live) you wrote about: 'What does this mean please?' >> Come on!! Exact bug with same register values, etc? Can't be!! >> Yes, it's a linker error but not the "Exact" bug! If Martin moves to VO 2.8 > It has the same exception handler code of 0xC0000005 so it is the same > bug caused the same way. I have posted my error log entry so that Robert > can extract the relevant info. 0xC0000005 is an 'Access Violation' and can have thousands of different causes. Where and when did you post your VO 2.8 error logs? Not on support.cavo.com. If you want to be sure that the issue is not lost, you need to post it there -- Robert van der Hulst AKA Mr. Data Vo2Jet & Vo2Ado Support VO Development Team www.heliks.nl
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 Prev: Phantom errors Next: VO2Oracle - storing and retrieving images in the database |