User Activity

  • Posted a comment on ticket #828 on Code::Blocks

    Running debuggee from codeblocks outputs this: Active debugger config: GDB/CDB debugger:Default Building to ensure sources are up-to-date Selecting target: Debug Adding source dir: C:\qemu\qemu_proj\qemu_debug\ Adding source dir: C:\ Adding file: C:\user\qemux64\qemu-system-i386_dbg.exe Changing directory to: C:/qemu/qemu_proj/qemu_debug/. Set variable: PATH=some paths Starting debugger: C:\user\cb_nightly\mingw64\bin\gdb.exe -nx -fullname -quiet -args C:/user/qemux64/qemu-system-i386_dbg.exe done...

  • Posted a comment on ticket #828 on Code::Blocks

    Gdb successfully runs my executable, but exits when executing "i frame" command. When cb uses this command, then this should be the reason of exiting gdb.

  • Posted a comment on discussion Open Discussion on tds2dbg

    tds2pdb has a wrong segMap structure definition: struct CVssSegMapSegDesc { ... WORD offset; /* Offset of logical segment within physical segment. !! Always 0. / !! WORD cbSeg; ///< Size of segment. These fields are defined as unsigned long (4 bytes) in Microsofts headers: typedef struct OMFSegMapDesc .... unsigned long offset; unsigned long cbSeg; } OMFSegMapDesc; Another error is probably the result that the uploaded tds2pdb.exe was compiled with 2-byte structure field alignment, that leads to...

  • Posted a comment on ticket #828 on Code::Blocks

    Look at the various mingw projects they provide GDB executables for windows. Yes, I used gdb from mingw. About 3) I'm not even sure what you're talking about. What do you mean crosscompiled exe? Crosscompiling here means building windows binaries under linux. I used mingw. p.s. This is not a place to discuss usage issues, just bug reports and feature requests. For general usage discussions please use the forum. The bug was in failed debugger attaching on windows. It was closed because I used 32-bit...

  • Modified a comment on ticket #828 on Code::Blocks

    FYI: 3) Not sure if this is a supported scenario (debugging a crosscompiled exe from an empty project). When not, it would be usefull to support this scenario. Seems like this scenario is not supported. Tried the 20 April 2019 build (11628) with 64-bit mingw gdb. Attach succeeds, but gdb immediately exits. When starting the executable from cb, it runs, but breakpoints are not hit. When pausing debuggee, gdb exits.

  • Posted a comment on ticket #828 on Code::Blocks

    FYI: 3) Not sure if this is a supported scenario (debugging a crosscompiled exe from an empty project). When not, it would be usefull to support this scenario. Seems like this scenario is not supported. Tried the 20 April 2019 build (11628) with 64-bit mingw gdb. Attach succeeds, but gdb immediately exits. When starting the executable from cb, it runs, but breakpoints are not hit. When pausing debuggee, gdb exits.

  • Posted a comment on ticket #828 on Code::Blocks

    Night builds don't contain gdb, where can I download gdb version for codeblocks? Official gdb site seems containing only linux distros.

  • Posted a comment on ticket #828 on Code::Blocks

    I'm running codeblocks on a windows host, I can't find night builds for this platform. The debugged exe is 64-bit, my installed codeblocks version is 32-bit, so this should be the problem. But windows binary download page (http://www.codeblocks.org/downloads/26#windows) don't offers different architectures, the architecture is even not mentioned and seems to be only 32-bit. Is there any other page with 64-bit builds for windows hosts?

View All

Personal Data

Username:
nevilad
Joined:
2019-05-17 10:12:21

Projects

  • No projects to display.

Personal Tools