Re: Dialog Editor Crash

Tech-Archive recommends: Fix windows errors by optimizing your registry

I worked all day Saturday on it and was able to come up with a pretty simple
sample project that reproduces the Resource Editor crash and the Find Symbol
bug. I sent both in as bug reports. We'll see what happens.

Great, can you paste the link to your bug report here - it'll give
others the opportunity to have a look at it and maybe verify it.

I haven't figured out a way to isolate the optimizer problems to any more
than the subroutine. Since it doesn't happen in debug you can't really break
at the point of the crash.

You can debug the optimised version if you set the appropriate debug
generation options on the project's C/C++ and Linker tabs. Also, have
a look for "Turn on Generation of Debug Information for the Release
Build" in your VC++ help.

As it's an optimised build the compiler will rearrange the code - so
lines of source don't always match and variables aren't often what the
debugger reports them to be - you can do it, but you have to
disbelieve a lot of what you get told and look a bit deeper, possibly
into the registers.

I'm not sure how one would find "incorrect code that happens to give correct
results without the optimizations". I'd like to see an example of how that is
possible. Can you think of an example of such a thing?

Not on the spur of the moment. I have reported a couple of such things
myself that I believed were clearly compiler optimisation bugs, only
to be told by MS that the code was incorrect - and indeed it was.
These things are difficult to spot if you're too close to the code, it
often pays to go through it with a fine tooth comb with a colleague.

BTW, is http://lab.msdn.microsoft.com/productfeedback/ the best place to
report VS2005 bugs? That's where I submitted them.

Yes. If you have blocking issues and need a solution quickly, it's
best to ring MS and report the bug. That way their official channels
will function to get you a workaround and/or a quick fix - if it's
feasible.

Dave
.

Relevant Pages

  • Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"
    ... Noone knows how many thousand bug reports have never reached lkml ... filing or get back to terminate the report. ... But I would like kernel people to become less egocentric ... Send _one_ email to lkml and you'll get forever spam to this address. ...
    (Linux-Kernel)
  • Re: 2.6.25-rc8: FTP transfer errors
    ... Yes, Mark, we used to do things that way for every bug in the kernel. ... We should be very careful about git-bisect. ... the developers, because when they think they might have fixed it, ... But I know that a report is a report, and even if I have a ...
    (Linux-Kernel)
  • Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"
    ... Noone knows how many thousand bug reports have never reached lkml ... filing or get back to terminate the report. ... But I would like kernel people to become less egocentric ... Send _one_ email to lkml and you'll get forever spam to this address. ...
    (Linux-Kernel)
  • Re: Linux 2.6.21
    ... The kernel Bugzilla currently contains 1600 open bugs. ... Adrian, why do you keep harping on this, and ignoring reality? ... I suspect some bug reports get ignored deliberately. ... engage some developers on a bug report. ...
    (Linux-Kernel)
  • Bugfix(59/8=APNIC), math jobs (was: JDEE/CGI/flashcards ...)
    ... bug report so I could fix the problem quickly. ... > Note that I said it "looks" incomplete and buggy, ... > high math skills. ...
    (comp.lang.lisp)