search for: debugbreak

Displaying 19 results from an estimated 19 matches for "debugbreak".

2011 Jul 26
2
[LLVMdev] Proposal for better assertions in LLVM
On Tue, Jul 26, 2011 at 10:56 AM, FlyLanguage <flylanguage at gmail.com> wrote: > #define ASSERT_STRM(cond, args) \ >> if (!(cond)) AssertionFailureStream(__FILE_**_, __LINE__) << args >> >> Note that there's no trailing semicolon, as this is supplied at the >> point where the macro is invoked. >> >> What do you think? >> >
2011 Jul 26
0
[LLVMdev] Proposal for better assertions in LLVM
...ou think? > > > Neat, but inducing a debug trap is even more useful on asserts > (optionally). > > > What's the best way to do that? I'd like to incorporate it into my > frontend's diagnostics. Depends on platform. asm {int 3} on x86, asm {trap} on ppc, DebugBreak on windows, etc.
2010 Aug 31
2
Splinter Cell Conviction
...DRM works correctly after to apply a patch on Wine 1.3.1 source. But, when i launch the game I have this error message : Code: ..\..\..\src\thread\ms\thread.cpp(328) : ASSERT FAILURE: Ret() wine: Unhandled exception 0x80000003 at address 0x7b8326d3 (thread 001f), starting debugger... 0x7b8326d3 DebugBreak+0x3 in kernel32: int $3 Modules: Module Address Debug info Name (131 modules) PE 240000- 256000 Deferred xinput1_3 PE 260000- 2c3000 Deferred lead3dengine PE 2d0000- 2e9000 Deferred leadd3dxenonr PE 2f0000- 3eb000 Deferred lead3doffline PE 3f0000- 3f7000...
2010 May 05
0
Splinter Cell: Conviction crashes
..._IOCTL cmd (9800012c) > fixme:iphlpapi:NotifyAddrChange (Handle 0xb1e8d8, overlapped 0xb1e8e0): stub > > > ..\..\..\src\thread\ms\thread.cpp(328) : ASSERT FAILURE: Ret() > wine: Unhandled exception 0x80000003 at address 0x7b832b63 (thread 0009), starting debugger... > 0x7b832b63 DebugBreak+0x3 in kernel32: int $3 > Modules: > Module Address Debug info Name (130 modules) > PE 240000- 2a1000 Deferred lead3dengine > PE 2b0000- 2c9000 Deferred leadd3dxenonr > PE 2d0000- 3cb000 Deferred lead3doffline > PE 3d0000- 3d7000 Deferred...
2011 Jul 26
2
[LLVMdev] Proposal for better assertions in LLVM
...t inducing a debug trap is even more useful on asserts >> (optionally). >> >> >> What's the best way to do that? I'd like to incorporate it into my >> frontend's diagnostics. >> > > Depends on platform. asm {int 3} on x86, asm {trap} on ppc, DebugBreak on > windows, etc. > > -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110726/4ca2b9c2/attachment.html>
2011 Jun 24
0
Wine release 1.3.23
...t Of Fate: Game freezes at loading 23736 Kingdom Heroes crashes due to missing msvcp80.dll.?find_last_of@?$basic_string at DU?$char_traits at D@std@@V?$allocator at D@2@@std@@QBEIPBDI at Z 23833 Black Buccaneer: media not detected (SecuROM 7.x) 24157 Tera Copy crashes on startup - kernel32.DebugBreak() taints frame pointer (Obsidium v1.x Software Protection System) 24350 Lord of the Rings Online Hardware Pixel shader enabled exits the game on startup. 24560 World of Goo demo needs msvcp80.dll.??$?8DU?$char_traits at D@std@@V?$allocator at D@1@@std@@YA_NABV?$basic_string at DU?$char_traits...
2012 Mar 02
3
[LLVMdev] Access Violation using ExecutionEngine on 64-bit Windows 8 Consumer Preview
...nction is called 3 or 4 times from my function like this: 0000000000C700A5 push rax 0000000000C700A6 mov esi,ecx 0000000000C700A8 sub rsp,20h 0000000000C700AC mov rax,76CBC490h 0000000000C700B6 call rax ; this is my call to DebugBreak() which goes first 0000000000C700B8 add rsp,20h 0000000000C700BC mov eax,10h 0000000000C700C1 call 00000000773A0DD0 0000000000C700C6 sub rsp,rax 0000000000C700C9 mov r8,rsp 0000000000C700CC mov dword ptr [r8],0 0000000000C700D3 mov eax,1...
2005 Oct 22
0
lotus WordPro problem
...:ole:StdMarshalImpl_ReleaseMarshalData could not map MID to stub manager, oxid=800000009, oid=3 err:ole:CoReleaseMarshalData IMarshal::ReleaseMarshalData failed with error 0x8001011d wine: Unhandled exception (thread 0009), starting debugger... WineDbg starting on pid 0x8 In 32 bit mode. 0x7bb5e3a4 DebugBreak+0x4 in kernel32: popl %ebp Modules: Module Address Debug info Name (80 modules) PE 0x00400000-008cf000 Deferred wordpro PE 0x03d90000-03d9c000 Deferred lwppann PE 0x040c0000-0424b000 Deferred wpenc70 PE 0x04c80000-04cbc0...
2019 Aug 14
9
[9.0.0 Release] Release Candidate 2 is here
Hello everyone, 9.0.0-rc2 was tagged yesterday from the release_90 branch at r368683. In the Git monorepo it's available as the llvmorg-9.0.0-rc2 tag. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc2 Binaries will be added as they become available. The tag went in roughly one week behind schedule (see "Upcoming Releases" at https://llvm.org), but
2004 Mar 31
1
wine segfaults and crashes my 2.4.x kernel
kernel is downloaded with up2date: [s2@katleriai s2]$ cat /etc/redhat-release && rpm -q glibc kernel && uname -r Red Hat Linux release 8.0 (Psyche) glibc-2.3.2-4.80.8 kernel-2.4.20-27.8 kernel-2.4.20-28.8 2.4.20-28.8 when i make wine to run setup.exe from WordViewer97, i am getting usual installer's window with two buttons. after pressing "Continue" i am getting
2019 Jul 29
10
[9.0.0 Release] Release Candidate 1 is here
Hi everyone, 9.0.0-rc1 was just tagged from the release_90 branch at r367217 (tagged as llvmorg-9.0.0-rc1 in the Git monorepo). Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc1 Binaries will be added as they become available. Please file bug reports for any issues you find as blockers of https://llvm.org/PR42474 Release testers: please start your engines, run the
2019 Sep 13
4
[9.0.0 Release] Release Candidate 5 is here
Hello everyone, 9.0.0-rc5 was just tagged from the release_90 branch at r371837. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc5. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc5 Binaries will be added as they become available. There is only a single change from rc4 to rc5. Once more, the hope is that this will be the last release candidate and that we can
2019 Dec 14
5
LLVM 9.0.1-rc3 has been tagged
Hi, I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading binaries. This will be the last release candidate unless there is a major problem. I'm planning to tag the final release on Dec 19. -Tom
2019 Sep 10
15
[9.0.0 Release] Release Candidate 4 is here
Hello again, 9.0.0-rc4 was just tagged from the release_90 branch at r371490. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc4. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc4 Binaries will be added as they become available. There are not a lot of changes from rc3 to rc4, and there are again no open release blockers, so I'm hoping this will be the last
2019 Nov 23
5
LLVM 9.0.1-rc1 Release has been tagged
Hi, I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload binaries. I've also updated the test-release.sh script to pull from GitHub instead of SVN, if you run into any issues with the new script, let me know. -Tom
2019 Dec 20
7
LLVM 9.0.1-final has been tagged
Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom
2019 Aug 30
9
[9.0.0 Release] Release Candidate 3 is here
Hello everyone, 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3 Binaries will be added as they become available. There are currently no open release blockers, which means if nothing new comes up, the final release could ship soon and this is
2019 Dec 07
6
LLVM 9.0.1-rc2 has been tagged
Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom
2019 Sep 17
18
[9.0.0 Release] Release Candidate 6 is here
Hello everyone, 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc6. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc6 This is the same as rc5 plus one very minor change (r371969) that still seemed good to pick up. I'm not allocating extra time for testing this one, expecting to tag