Displaying 6 results from an estimated 6 matches for "check32".
Did you mean:
check2
2012 Mar 07
1
[LLVMdev] Problem with x86 32-bit debug information ?
...nd set a breakpoint to the check routine and
executes to the breakpoint, I've got:
Breakpoint 1, check (result=0x601110, expect=0x601020, n=53) at check.c:7
7 {
As you can see I can inspect 'n' value.
Now if I compile for x86 32-bit as follows:
clang -m32 -O2 -g check.c main.c -o check32
When I do gdb check32 and set a breakpoint to the check routine and
executes to the breakpoint, I've got:
Breakpoint 1, check (result=<value optimized out>,
expect=<value optimized out>, n=0) at check.c:7
7 {
As you can see I can NOT inspect 'n' value. Is there a w...
2012 Mar 07
1
[LLVMdev] Problem with x86 32-bit debug information ?
...gt; executes to the breakpoint, I've got:
>
> Breakpoint 1, check (result=0x601110, expect=0x601020, n=53) at check.c:7
> 7 {
>
> As you can see I can inspect 'n' value.
>
> Now if I compile for x86 32-bit as follows:
>
> clang -m32 -O2 -g check.c main.c -o check32
>
> When I do gdb check32 and set a breakpoint to the check routine and
> executes to the breakpoint, I've got:
>
> Breakpoint 1, check (result=<value optimized out>,
> expect=<value optimized out>, n=0) at check.c:7
> 7 {
>
> As you can see I can N...
2012 Mar 07
3
[LLVMdev] Problem with x86 32-bit debug information ?
...gt; executes to the breakpoint, I've got:
>
> Breakpoint 1, check (result=0x601110, expect=0x601020, n=53) at check.c:7
> 7 {
>
> As you can see I can inspect 'n' value.
>
> Now if I compile for x86 32-bit as follows:
>
> clang -m32 -O2 -g check.c main.c -o check32
>
> When I do gdb check32 and set a breakpoint to the check routine and
> executes to the breakpoint, I've got:
>
> Breakpoint 1, check (result=<value optimized out>,
> expect=<value optimized out>, n=0) at check.c:7
> 7 {
>
> As you can see I can N...
2012 Mar 08
0
[LLVMdev] Problem with x86 32-bit debug information ?
...9;ve got:
>>
>> Breakpoint 1, check (result=0x601110, expect=0x601020, n=53) at check.c:7
>> 7 {
>>
>> As you can see I can inspect 'n' value.
>>
>> Now if I compile for x86 32-bit as follows:
>>
>> clang -m32 -O2 -g check.c main.c -o check32
>>
>> When I do gdb check32 and set a breakpoint to the check routine and
>> executes to the breakpoint, I've got:
>>
>> Breakpoint 1, check (result=<value optimized out>,
>> expect=<value optimized out>, n=0) at check.c:7
>> 7 {
>...
2012 Mar 09
0
[LLVMdev] Problem with x86 32-bit debug information ?
..., check (result=0x601110, expect=0x601020, n=53) at
> check.c:7
> >> 7 {
> >>
> >> As you can see I can inspect 'n' value.
> >>
> >> Now if I compile for x86 32-bit as follows:
> >>
> >> clang -m32 -O2 -g check.c main.c -o check32
> >>
> >> When I do gdb check32 and set a breakpoint to the check routine and
> >> executes to the breakpoint, I've got:
> >>
> >> Breakpoint 1, check (result=<value optimized out>,
> >> expect=<value optimized out>, n=0) at...
2004 Dec 31
5
School Software with WINE
...ll get this:
suse:~/.wine/fake_windows/ProCare # rm NET
NETAPI.DLL NETAPI32.DLL NETBIOS.DLL
suse:~/.wine/fake_windows/ProCare # rm NET* -f
suse:~/.wine/fake_windows/ProCare # ls
. BAKPR.INI MSVBVM60.DLL PRO32.EXE PROPR.INI
PRO_PR32.EXE RDini index.html.1
.. CHECK32.EXE MSVCRT20.DLL PROAP.INI PRO_AP32.EXE
PocketPC REPAIR32.EXE msvcrt.dll
BAKAP.INI Help OLE32.DLL PROAR.INI PRO_AR32.EXE
ProCare.INI RPCRT4.DLL
BAKAR.INI Install OLEAUT32.DLL PROCBT32.EXE PRO_IR32.EXE
ProCare.INI~ VISDATA.EXE
suse:~/.wine/fake_windows/ProC...