On 10/20/06, Mikhail Fursov <[EMAIL PROTECTED]> wrote:
On 10/20/06, Weldon Washburn <[EMAIL PROTECTED]> wrote: > > This sounds very much like what I experienced before I did the > below. When > the above dialog box opens, are you running from msvc debugger or from a > msdos console window? It seems msvc 2003/2005 can't find the debug > symbols > if drlvm is run from command line and hits a debug event such as a > sigsegv, assert(0) or int 3. > I have the problem with stack only when I run from console window. When I run from MSVC it works fine. Not a big problem but I think it's better for us to find the answer why the stack is not available...
hmm... It looks like the problem you have is identical to what I experienced. I agree it would be better to find out why debug symbols are not available. We definitely need to be able to debug the VM in the field. Dumping what amounts to a bunch of hex is not acceptable. I tried multiple different ways to point MSVC at the *.PDB files. Nothing worked. --
Mikhail Fursov
-- Weldon Washburn Intel Middleware Products Division
