Patch is ok. Please go ahead and apply.
Thanks,
Kai
2014-10-15 20:14 GMT+02:00 Jacek Caban :
> For SOCKADDR_INET.
>
> ---
> mingw-w64-headers/include/netioapi.h | 1 +
> 1 file changed, 1 insertion(+)
>
>
>
> --
> Compr
For SOCKADDR_INET.
---
mingw-w64-headers/include/netioapi.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/mingw-w64-headers/include/netioapi.h b/mingw-w64-headers/include/netioapi.h
index 8355136..9e7f67d 100644
--- a/mingw-w64-headers/include/netioapi.h
+++ b/mingw-w64-headers/include/net
Kai Tietz 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 unwinding pretty much.
>
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 so
>
> 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.
---
Alexander Shukaev
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
> Exception Dat
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
2014-10-15 10:05 GMT+02:00 Alexander Shukaev :
> 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: c0
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 exactly
>
> Hi, Alexander!
>
Hey Alexey,
> 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 backtrace from G
15 окт. 2014 г., в 11:38, Alexander Shukaev написал(а):
> 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
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 th
12 matches
Mail list logo
