A
Alex
Hello everybody,
I've been working for days on a "twilight zone" bug and I can't make any
sense of it. This is in an application that was developped on XP and that
was modified to handle Vista. Other than using the virtual store for some
config information, it doesn't do anything fancy. The strange thing is that
when the application is executed without an active internet connection,
there is a crash in the application for some of our clients. I've made a
special version with a log to try and pinpoint the crash culprit and
surprisingly, the software doesn't crash anymore but it's still behaving
strangely (we suspect memory corruption might be occuring). This occurs for
Vista clients only. When the software is executed with an internet
connection, there are no problems.
The strange thing is that we don't access the internet at all in these
scenarios... I have hunch, fron the info I've managed the gather, that the
problem might be occuring while accessing registry values (reading them),
but it could be a false trail.
I'm not very knowledgable of Vista, so I was wondering what, in Vista, could
cause something like that to happen?
Thanks,
Alex.
I've been working for days on a "twilight zone" bug and I can't make any
sense of it. This is in an application that was developped on XP and that
was modified to handle Vista. Other than using the virtual store for some
config information, it doesn't do anything fancy. The strange thing is that
when the application is executed without an active internet connection,
there is a crash in the application for some of our clients. I've made a
special version with a log to try and pinpoint the crash culprit and
surprisingly, the software doesn't crash anymore but it's still behaving
strangely (we suspect memory corruption might be occuring). This occurs for
Vista clients only. When the software is executed with an internet
connection, there are no problems.
The strange thing is that we don't access the internet at all in these
scenarios... I have hunch, fron the info I've managed the gather, that the
problem might be occuring while accessing registry values (reading them),
but it could be a false trail.
I'm not very knowledgable of Vista, so I was wondering what, in Vista, could
cause something like that to happen?
Thanks,
Alex.