You can also use backtrace-mingw:
http://code.google.com/p/backtrace-mingw/
a much more recent version (public domain) is found here:
http://wiki.eduke32.com/wiki/Building_EDuke32_on_Windows
http://wiki.eduke32.com/wiki/Acquiring_the_EDuke32_Source_Code (see daily
snapshots)
compile it with:
Hey everyone,
Could you guys give me a hint how to properly debug something on Windows
with GDB?
I usually don't use GDB to find out causes of crashing, i.e. I either infer
them from the code or find it out through logging facilities. One of the
reasons why I almost never use GDB on Windows is
15 окт. 2014 г., в 11:38, Alexander Shukaev haroo...@gmail.com написал(а):
Hey everyone,
Could you guys give me a hint how to properly debug something on Windows with
GDB?
I usually don't use GDB to find out causes of crashing, i.e. I either infer
them from the code or find it out
When the application crashes it shows the following:
Fault Module Name: StackHash_e7de
Fault Module Version: 0.0.0.0
Fault Module Timestamp:
Exception Offset: PCH_E1_FROM_ntdll+0x0009B13A
Exception Code: c005
Exception Data: 0008
This resembles
2014-10-15 10:05 GMT+02:00 Alexander Shukaev haroo...@gmail.com:
When the application crashes it shows the following:
Fault Module Name: StackHash_e7de
Fault Module Version: 0.0.0.0
Fault Module Timestamp:
Exception Offset: PCH_E1_FROM_ntdll+0x0009B13A
Exception
On 15.10.2014 11:52, Alexander Shukaev wrote:
First you need build application with debug info using CFLAGS like «-Og
-g» and don’t strip result binaries.
When I was asking this question it was already implied as I am of course
aware of these details.
After this you can get useful
Alexander Shukaev haroo...@gmail.com
writes:
When the application crashes it shows the following:
Fault Module Name: StackHash_e7de
Fault Module Version: 0.0.0.0
Fault Module Timestamp:
Exception Offset: PCH_E1_FROM_ntdll+0x0009B13A
Exception Code: c005
Are you running the application from gdb? Seeing the above makes me
think you are not.
The GDB output was presented in the very first post. The one that you refer
to is simply a crash report generated by Windows itself. I included it
merely to provide some clues.
Hi,
for sure there are some issues in gdb about debugging pe and pe+ coff
executables in some scenarios. For pe+ ones the backtrace shown by
gdb is much more reliable then for the 32-bit case, as pe+ makes use
of the function-tables, which helps on unwinding pretty much.
Nevertheless there are
Kai Tietz ktiet...@googlemail.com writes:
for sure there are some issues in gdb about debugging pe and pe+ coff
executables in some scenarios. For pe+ ones the backtrace shown by
gdb is much more reliable then for the 32-bit case, as pe+ makes use
of the function-tables, which helps on
On 2012-7-21 15:07, Eran Ifrah wrote:
On Sat, Jul 21, 2012 at 7:59 AM, asmwarrior
asmwarrior-re5jqeeqqe8avxtiumw...@public.gmane.org
mailto:asmwarr...@gmail.com wrote:
On 2012-7-21 11:38, K. Frank wrote:
As I mentioned above, my gdb version is 7.3.0.
You can try a
2012/7/21 asmwarrior asmwarr...@gmail.com
On 2012-7-21 15:07, Eran Ifrah wrote:
On Sat, Jul 21, 2012 at 7:59 AM, asmwarrior
asmwarrior-re5jqeeqqe8avxtiumw...@public.gmane.org mailto:
asmwarr...@gmail.com wrote:
On 2012-7-21 11:38, K. Frank wrote:
As I mentioned above, my
Hi guys,
Regarding GDB and Python:
I've got some WIP Python patches that were created for Necessitas Qt
Creator's NDK GDB for Android. They've since been merged into the
Google NDK:
https://android-review.googlesource.com/#/c/38501/
Using the patches in that merge request, it's possible to
2012/5/14 Antony Riakiotakis kal...@gmail.com
Hi,
First, good news:
MinGW-w64 support for blender is getting more complete by the day, to
the point where users download and test (and may even prefer, due to
the speed increase ;) ) mingw-w64 builds. There have been a few
compiler-related
Hmmm...I really can't say.. unfortunately, openmp destabilizes the
build (crash when rendering subdivision modified objects) so it may be
causing the error with threading on your build. Also we bundle the
pthread library that came from a different MinGW64 build, which may
cause the issues with
Hi Ruben!
On Mon, May 14, 2012 at 2:27 PM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote:
2012/5/14 Antony Riakiotakis kal...@gmail.com
Hi,
First, good news:
MinGW-w64 support for blender is getting more complete by the day, ...
...
I decided to build blender from source, which worked
Ah, looks like the reason for the strange behaviour was my using
release with debug info build type for cmake. Optimizations play funky
with the debugger it seems. Now all is in order...phew.
So, summarizing again for reference:
* Make sure python 2.7 is installed
* Make sure you don't enable
17 matches
Mail list logo
