You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Weldon Washburn <we...@gmail.com> on 2006/10/20 15:20:30 UTC
[drlvm] debugging on msvc -- getting debug symbols to load
Suddenly I am unable to debug msvc 2003. It won't load the debug symbols I
tried installing msvc 2005 but it still won't load the debug symbols.
The following seems to work. Does anyone else see this? Is there an easier
way to do this?
1)
Create a new and empty project
2)
On the Project pulldown, select "newproject Properties"
3)
put something like the following in the "Command" window
c:\t_harmony\drlvm\trunk\build\win_ia32_msvc_debug\deploy\jre\bin\java.exe
4)
put something like the following in the "Command Arguments" window
-Xbootclasspath/p:.;mmtk.jar -Xem:jet -Xms512m -Xms512m -version
TestSemiSpace 1
5)
build the new and empty project to keep msvc happy
6)
start debugging -- push F5
NOTE: I like to put an "__asm{int 3}" in the C/C++ code. This will force
the binary to always call the debugger.
--
Weldon Washburn
Intel Middleware Products Division
Re: [drlvm] debugging on msvc -- getting debug symbols to load
Posted by Rana Dasgupta <rd...@gmail.com>.
Hi Weldon,
I am sorry to to see that you may be still having problems with the
VS.Net debugger. I use it all the time, and everything( BP's, watch, memory
and thread windows ) works as expected. If you haven't done so alread, could
you please give this a shot?
devenv /debugexe whatever-command-line-executable-is
needed-to-work-from-this-dos-window
(absolute paths please )
The MS debug PE's are quite sophisticated now and have the embedded info
about symbol file locations, default source file locations, symbol mapping,
etc. Debugger messup is not fun.
Hope this helps,
Rana
> On 10/20/06, Weldon Washburn <we...@gmail.com> wrote:
> >
> > On 10/20/06, Mikhail Fursov <mi...@gmail.com> wrote:
> > >
> > > On 10/20/06, Weldon Washburn <we...@gmail.com> 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
> >
> >
>
Re: [drlvm] debugging on msvc -- getting debug symbols to load
Posted by Weldon Washburn <we...@gmail.com>.
On 10/20/06, Mikhail Fursov <mi...@gmail.com> wrote:
>
> On 10/20/06, Weldon Washburn <we...@gmail.com> 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
Re: [drlvm] debugging on msvc -- getting debug symbols to load
Posted by Mikhail Fursov <mi...@gmail.com>.
On 10/20/06, Weldon Washburn <we...@gmail.com> 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...
--
Mikhail Fursov
Re: [drlvm] debugging on msvc -- getting debug symbols to load
Posted by Weldon Washburn <we...@gmail.com>.
On 10/20/06, Mikhail Fursov <mi...@gmail.com> wrote:
>
> The way you debugging should work.
>
> I use MSVC + Visual Assist as code browser + I do not use __asm(int
> 3)-like
> breakpoints, therefore working with complete projects is more convenient
> for
> me.
Actually all that is required is a single int 3. It simply activates the
debugger. Normal breakpoints can be set once the int 3 is hit.
BTW I noticed that when VM is crashed the "Debug" button in the dialog opens
> VS debugger with all stack lost...(is it a conflict with thread stack
> dumping functionality?)
> So I always run from MSVC and use integrated breakpoints functionality.
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.
On 10/20/06, Weldon Washburn <we...@gmail.com> wrote:
> >
> > On 10/20/06, Mikhail Fursov <mi...@gmail.com> wrote:
> > >
> > > Weldon,
> > > I use MSVC 2003 for debugging every day and everything works fine.
> > > Did you try drlvm/trunk/buld/msvc_2003 build? It's not complete (no
> > > vmcore,
> > > no gc), but it runs debug session OK to me.
> >
> >
> > Actually, I am in the process of moving to msvc 2005. There would need
> to
> > be another directory called .../msvc_2005. I am too lazy to maintain
> the
> > msvc files. Doing the below seems less maintenance (but I could be
> > wrong!)
> >
> >
> > On 10/20/06, Weldon Washburn <we...@gmail.com> wrote:
> > > >
> > > > Suddenly I am unable to debug msvc 2003. It won't load the debug
> > > > symbols I
> > > > tried installing msvc 2005 but it still won't load the debug
> symbols.
> > > >
> > > > The following seems to work. Does anyone else see this? Is there
> an
> > > > easier
> > > > way to do this?
> > > >
> > > > 1)
> > > > Create a new and empty project
> > > >
> > > > 2)
> > > > On the Project pulldown, select "newproject Properties"
> > > >
> > > > 3)
> > > > put something like the following in the "Command" window
> > > >
> > > >
> > >
> >
> c:\t_harmony\drlvm\trunk\build\win_ia32_msvc_debug\deploy\jre\bin\java.exe
> > > >
> > > > 4)
> > > > put something like the following in the "Command Arguments" window
> > > >
> > > > -Xbootclasspath/p:.;mmtk.jar -Xem:jet -Xms512m -Xms512m -version
> > > > TestSemiSpace 1
> > > >
> > > > 5)
> > > > build the new and empty project to keep msvc happy
> > > >
> > > > 6)
> > > > start debugging -- push F5
> > > >
> > > > NOTE: I like to put an "__asm{int 3}" in the C/C++ code. This will
> > > force
> > > > the binary to always call the debugger.
> > > >
> > > >
> > > >
> > > > --
> > > > Weldon Washburn
> > > > Intel Middleware Products Division
> > > >
> > > >
> > >
> > >
> > > --
> > > Mikhail Fursov
> > >
> > >
> >
> >
> > --
> > Weldon Washburn
> > Intel Middleware Products Division
> >
> >
>
>
> --
> Mikhail Fursov
>
>
--
Weldon Washburn
Intel Middleware Products Division
Re: [drlvm] debugging on msvc -- getting debug symbols to load
Posted by Mikhail Fursov <mi...@gmail.com>.
The way you debugging should work.
I use MSVC + Visual Assist as code browser + I do not use __asm(int 3)-like
breakpoints, therefore working with complete projects is more convenient for
me.
BTW I noticed that when VM is crashed the "Debug" button in the dialog opens
VS debugger with all stack lost...(is it a conflict with thread stack
dumping functionality?)
So I always run from MSVC and use integrated breakpoints functionality.
On 10/20/06, Weldon Washburn <we...@gmail.com> wrote:
>
> On 10/20/06, Mikhail Fursov <mi...@gmail.com> wrote:
> >
> > Weldon,
> > I use MSVC 2003 for debugging every day and everything works fine.
> > Did you try drlvm/trunk/buld/msvc_2003 build? It's not complete (no
> > vmcore,
> > no gc), but it runs debug session OK to me.
>
>
> Actually, I am in the process of moving to msvc 2005. There would need to
> be another directory called .../msvc_2005. I am too lazy to maintain the
> msvc files. Doing the below seems less maintenance (but I could be
> wrong!)
>
>
> On 10/20/06, Weldon Washburn <we...@gmail.com> wrote:
> > >
> > > Suddenly I am unable to debug msvc 2003. It won't load the debug
> > > symbols I
> > > tried installing msvc 2005 but it still won't load the debug symbols.
> > >
> > > The following seems to work. Does anyone else see this? Is there an
> > > easier
> > > way to do this?
> > >
> > > 1)
> > > Create a new and empty project
> > >
> > > 2)
> > > On the Project pulldown, select "newproject Properties"
> > >
> > > 3)
> > > put something like the following in the "Command" window
> > >
> > >
> >
> c:\t_harmony\drlvm\trunk\build\win_ia32_msvc_debug\deploy\jre\bin\java.exe
> > >
> > > 4)
> > > put something like the following in the "Command Arguments" window
> > >
> > > -Xbootclasspath/p:.;mmtk.jar -Xem:jet -Xms512m -Xms512m -version
> > > TestSemiSpace 1
> > >
> > > 5)
> > > build the new and empty project to keep msvc happy
> > >
> > > 6)
> > > start debugging -- push F5
> > >
> > > NOTE: I like to put an "__asm{int 3}" in the C/C++ code. This will
> > force
> > > the binary to always call the debugger.
> > >
> > >
> > >
> > > --
> > > Weldon Washburn
> > > Intel Middleware Products Division
> > >
> > >
> >
> >
> > --
> > Mikhail Fursov
> >
> >
>
>
> --
> Weldon Washburn
> Intel Middleware Products Division
>
>
--
Mikhail Fursov
Re: [drlvm] debugging on msvc -- getting debug symbols to load
Posted by Weldon Washburn <we...@gmail.com>.
On 10/20/06, Mikhail Fursov <mi...@gmail.com> wrote:
>
> Weldon,
> I use MSVC 2003 for debugging every day and everything works fine.
> Did you try drlvm/trunk/buld/msvc_2003 build? It's not complete (no
> vmcore,
> no gc), but it runs debug session OK to me.
Actually, I am in the process of moving to msvc 2005. There would need to
be another directory called .../msvc_2005. I am too lazy to maintain the
msvc files. Doing the below seems less maintenance (but I could be wrong!)
On 10/20/06, Weldon Washburn <we...@gmail.com> wrote:
> >
> > Suddenly I am unable to debug msvc 2003. It won't load the debug
> > symbols I
> > tried installing msvc 2005 but it still won't load the debug symbols.
> >
> > The following seems to work. Does anyone else see this? Is there an
> > easier
> > way to do this?
> >
> > 1)
> > Create a new and empty project
> >
> > 2)
> > On the Project pulldown, select "newproject Properties"
> >
> > 3)
> > put something like the following in the "Command" window
> >
> >
> c:\t_harmony\drlvm\trunk\build\win_ia32_msvc_debug\deploy\jre\bin\java.exe
> >
> > 4)
> > put something like the following in the "Command Arguments" window
> >
> > -Xbootclasspath/p:.;mmtk.jar -Xem:jet -Xms512m -Xms512m -version
> > TestSemiSpace 1
> >
> > 5)
> > build the new and empty project to keep msvc happy
> >
> > 6)
> > start debugging -- push F5
> >
> > NOTE: I like to put an "__asm{int 3}" in the C/C++ code. This will
> force
> > the binary to always call the debugger.
> >
> >
> >
> > --
> > Weldon Washburn
> > Intel Middleware Products Division
> >
> >
>
>
> --
> Mikhail Fursov
>
>
--
Weldon Washburn
Intel Middleware Products Division
Re: [drlvm] debugging on msvc -- getting debug symbols to load
Posted by Mikhail Fursov <mi...@gmail.com>.
Weldon,
I use MSVC 2003 for debugging every day and everything works fine.
Did you try drlvm/trunk/buld/msvc_2003 build? It's not complete (no vmcore,
no gc), but it runs debug session OK to me.
On 10/20/06, Weldon Washburn <we...@gmail.com> wrote:
>
> Suddenly I am unable to debug msvc 2003. It won't load the debug
> symbols I
> tried installing msvc 2005 but it still won't load the debug symbols.
>
> The following seems to work. Does anyone else see this? Is there an
> easier
> way to do this?
>
> 1)
> Create a new and empty project
>
> 2)
> On the Project pulldown, select "newproject Properties"
>
> 3)
> put something like the following in the "Command" window
>
> c:\t_harmony\drlvm\trunk\build\win_ia32_msvc_debug\deploy\jre\bin\java.exe
>
> 4)
> put something like the following in the "Command Arguments" window
>
> -Xbootclasspath/p:.;mmtk.jar -Xem:jet -Xms512m -Xms512m -version
> TestSemiSpace 1
>
> 5)
> build the new and empty project to keep msvc happy
>
> 6)
> start debugging -- push F5
>
> NOTE: I like to put an "__asm{int 3}" in the C/C++ code. This will force
> the binary to always call the debugger.
>
>
>
> --
> Weldon Washburn
> Intel Middleware Products Division
>
>
--
Mikhail Fursov