Sorry about that. It seems that I have been doing something wrong; most probably did not have the debug symbols anyway?. I tried it again and now I can step into the sources.
Thanks On Wed, May 9, 2012 at 10:52 AM, André Pönitz < [email protected]> wrote: > On Wed, May 09, 2012 at 01:12:45AM -0700, Mohammad Mirzadeh wrote: > > Ok I'm not sure what I'm doing wrong but when I attach the debugger to > > the process it only brings up the disassembler and does not go into > > the source. I have the .pro file based on which the make file was > > generated, but I'm not sure how I should be using it when I'm > > attaching the debugger to a process? > > If you see only assembler for a stack frame it mean you don't have debug > information and/or sources available for the current location. > > There are several possible reasons; > > - you attached while the process was in some library for > which you don't have debuginfo installed (happens often > for glib eventloop or similar) > > - you attach to process compiled without debug info (often > called "Release" build) > > - the debug info is there, but the debugger did not pick it up > > To find out which case you are in, please attach the full debugger > log (right pane of Windows->Views->Debugger Log) > > Andre' >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
