debugging problem - winedbg: single stepping until exit from function, which has no line number information
hello i'm on a project with wine but i can't get it debugged. not even a small hello world. here is the output of the hello world. My system opensuse 10.2 anyone help plz? Winedbg - Output: marcel(a)marcel-laptop-lan:~/prog/m5/m5/debug/src> winedbg m5.exe.so preloader: Warning: failed to reserve range 00000000-60000000 WineDbg starting on pid 000a 0x7b870749: movl %edi,0x0(%esp) Wine-dbg>step Single stepping until exit from function, which has no line number information. Invalid address (0x7b87074e) for breakpoint 0, disabling it Process of pid=000a has terminated Wine-dbg> Code: #ifdef HAVE_CONFIG_H #include <config.h> #endif #include <windows.h> int __stdcall WinMain (HINSTANCE hInst, HINSTANCE hPrev, LPSTR lpCmd, int nShow) { MessageBox (NULL, "Hello, Windows!", "Hello", MB_OK); int test = 0; test = 1000; test += 100; return 0; } Configure-Output: cd '/home/marcel/prog/m5/m5/debug' && CC="winegcc" CXX="wineg++" LD="ld" CXXFLAGS="-O0 -gdwarf-2 -g3" "/home/marcel/prog/m5/m5/configure" --enable-debug=full checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether wineg++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of wineg++... gcc3 checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... winegcc checking whether we are using the GNU C compiler... yes checking whether winegcc accepts -g... yes checking for winegcc option to accept ISO C89... none needed checking dependency style of winegcc... gcc3 checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ld used by winegcc... ld checking if the linker (ld) is GNU ld... yes checking for ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... winegcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... wineg++ -E checking for g77... no checking for f77... no checking for xlf... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for f90... no checking for xlf90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for f95... no checking for fort... no checking for xlf95... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from winegcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if winegcc supports -fno-rtti -fno-exceptions... no checking for winegcc option to produce PIC... -fPIC checking if winegcc PIC flag -fPIC works... yes checking if winegcc static flag -static works... no checking if winegcc supports -c -o file.o... yes checking whether the winegcc linker (ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by wineg++... ld checking if the linker (ld) is GNU ld... yes checking whether the wineg++ linker (ld) supports shared libraries... yes checking for wineg++ option to produce PIC... -fPIC checking if wineg++ PIC flag -fPIC works... yes checking if wineg++ static flag -static works... no checking if wineg++ supports -c -o file.o... yes checking whether the wineg++ linker (ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands *** Erfolg *** Make Output: cd '/home/marcel/prog/m5/m5/debug/src' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" gmake m5 if wineg++ -DHAVE_CONFIG_H -I. -I/home/marcel/prog/m5/m5/src -I.. -O0 -gdwarf-2 -g3 -MT m5.o -MD -MP -MF ".deps/m5.Tpo" -c -o m5.o /home/marcel/prog/m5/m5/src/m5.cpp; then mv -f ".deps/m5.Tpo" ".deps/m5.Po"; else rm -f ".deps/m5.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CXX --mode=link wineg++ -O0 -gdwarf-2 -g3 -o m5 -mwindows m5.o wineg++ -O0 -gdwarf-2 -g3 -o m5 -mwindows m5.o *** Erfolg *** --------------------------------- Kennt man wirklich jeden über 3 Ecken? Die Antworten gibt's bei Yahoo! Clever.
participants (1)
-
marcel busse