Displaying 5 results from an estimated 5 matches for "hheap".
Did you mean:
heap
2008 May 09
4
VB6 and wine_get_unix_file_name
...ix_file_name in VB6
programs.
Private Declare Function lstrcpyA Lib "kernel32.dll" (ByVal lpString1 As
String, ByVal lpString2 As Long) As Long
Public Declare Function GetProcessHeap Lib "kernel32" () As Long
Public Declare Function HeapFree Lib "kernel32" (ByVal hHeap As Long, ByVal
dwFlags As Long, IpMem As Any) As Long
Public Declare Function wine_get_unix_file_name Lib "kernel32" (ByVal
lpszSrc As String) As Long
Public Function GetUnixPath(ByVal sPath As String) As String
Dim ptr As Long
Dim sBuffer As String * 255
ptr = wine_ge...
2008 Aug 25
1
Please die if you wait "too long" RtlpWaitForCriticalSection
I'm receiving the following error in a custom app:
err:ntdll:RtlpWaitForCriticalSection section 0x110048 "heap.c: main
process heap section" wait timed out in thread 001a, blocked by 001c,
retrying (60 sec)
wine: Critical section 00110048 wait failed at address 0x7bc3ad00
(thread 001a), starting debugger...
err:ntdll:RtlpWaitForCriticalSection section 0x110048 "heap.c: main
2008 Jul 26
0
No subject
...erstanding why I seemed to be getting heap corruption
(when I had the "before" call) when I'm not even supposed to be
calling it due to the guarded if statement. From MSDN Calling
HeapFree twice with the same pointer can cause heap corruption
if (g_pTrades != NULL){
::HeapFree(hHeap, 0, g_pTrades);
}
2008 Aug 27
1
Re: Please die if you wait "too long" RtlpWaitForCriti
Dee Ayy wrote:
> On Mon, Aug 25, 2008 at 12:44 AM, vitamin <wineforum-user at winehq.org> wrote:
>
> > Try:
> >
> > Code:
> > $ wine cmd
> > c:> echo "some stuff" | myexe
> >
>
> Interesting way to run wine. However, I get the same response.
Then either your program is buggy or Wine's cmd doesn't fully implement what
2008 Aug 28
0
Re: Please die if you wait "too long" RtlpWaitForCriti
...'t understand.
> 1) My logic bug: There was no need to call the following before my
> code block -- I thought I was being cautious. (The MTAPI says to call
> it after). My app seems to be working fine now without this initial
> HeapFree.
> if (g_pTrades != NULL)
> ::HeapFree(hHeap, 0, g_pTrades);
The check for NULL is extra. HeepFree (same as normal free() ) ignores NULL pointers. So most likely you are freeing something you did not allocate.
Or as you said - freeing something twice. HeepFree (as well as normal free) does not modify the passed in pointer.