You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree:
0e7ad1c367
3096/hle/bufferc
3096/qcom/clamp
3096/spirv/warp
3096/vk/drain_pending_build
3096/vk/pipeline_compilation
Kernel
Update-some-barriers-test
android6
atomicops-mxwell
bcn-ternary-soft
bufferbatching
bundle-qt
camille/qcom-clamp
chore/NamespaceIndentation
chore/chore
civa
descriptor
descriptor_pool_opt
descriptor_set
disable-vap
discfix
display-modified-settings-first
dmnt2
dynarm7345
dynarmic-coproc
dynarmic-ppc64
eden-orbis-ps4
eds-true-adreno-fixes
eds-true-adreno-fixes-pre-0.1.0
ffmpeg-cross-compile
fix-fsr-crash-linux-waw
fix/cyrillic_paths
fix/discord-rpc
fix/gbh_test
flatopsfixes23485
freebsd-cubeb
fs-try
fs_external_dlcupdates
install-vulkan-ps1-fix-windows-on-arm
interval-zero
lanobu
liz-crash-dumps-solaris
liz-dynarmic-backport-waitpkg
liz-dynarmic-macos-fbsd-port
liz-get-rid-of-mcl-intrusive-list
liz-heaptrack-fix
liz-no-rtti-allowance
lizzie/core-inline-optional-ptr
lizzie/dynarmic-verbose-ndebug
lizzie/fix-vic-msvc-attempt-2
lizzie/openbsd-78-fix
lizzie/spinlock-to-cpp
lizzie/stack-fibers-vector
lizzie/test-evil-0
lizzie/vic-test-revert1
lm3-regression/1-of-3
lm3-regression/2-of-3
lm3-regression/shader-to-common
lock-term-1
macos-sqbuild
macroify-surface-stuffs
master
memsetopsyscallavoid
mmap-fixews
msvc-debug
msvc_fix-debug-build
mutliplayer-filter-better1
n64
nce-strx
nce_cpp
netgate1
netusejthreadstuff
no-d24
pagetable-clustering
pintocputhing
pipelinederivative
port/lr
qcom-weird-vk-ftz
quick-fix
refactoreds2
release/0.0.3
release/0.0.4
release/0.1.0
rem-dup-applet-launch
remove-unused-fastmem-fallback
reorder-menu-game-per-config
revert-1240cd43d70a502508115c9abb12f7ef27e1ca4e
revert-2695
revert-4758e126b863da560bf30a00deda3bb44e26b7fa
revert-7eb5710f353798b05b8860187e2728f7795717a0
revert-eed703bc81214a47a5fc7bd3abf22152cbd5c40b
scmfix-worktree
selfhost0
shaderwipe15
showcase
showcase2
simp-word-man1
sjkdbsdfjkbsdf-2834
smartqueryreset
spookymansionreducecpuusage
static-linux
stuffmadeforfun
sured-revert
techno48473719
test-revert-gpu-optim
test2
teto-territory
true-eds
true-eds-graphics
true-eds-pre-0.0.1
vk-fix-oom-force-maller-buffers
vk-surface-andpc
vulkan-thingy
woa-turnip-expr
worekrs467584
xbzk-debug-knobs-from-kotlin
xbzk-dynarmic-x64-regalloc-dup-args
xbzk-mci-bare-minimum-boot-fix
xbzk-saf-recursive-write-with-permission-request
0.0.0
0.0.1-pre-alpha
0.0.2-pre-alpha
test-tag1
test-tag2
v0.0.3
v0.0.3-rc1
v0.0.3-rc2
v0.0.3-rc3
v0.0.3.git
v0.0.4
v0.0.4-rc1
v0.0.4-rc2
v0.0.4-rc2.test
v0.0.4-rc2.test2
v0.0.4-rc3
v0.0.4-rc3.test1
v0.0.4-rc3.test2
v0.0.4.test
v0.1.0-rc1
${ noResults }
eden/.appveyor
* gdbstub: fix IsMemoryBreak() returning false while connected to client As a result, the only existing codepath for a memory watchpoint hit to break into GDB (InterpeterMainLoop, GDB_BP_CHECK, ARMul_State::RecordBreak) is finally taken, which exposes incorrect logic* in both RecordBreak and ServeBreak. * a blank BreakpointAddress structure is passed, which sets r15 (PC) to NULL * gdbstub: DynCom: default-initialize two members/vars used in conditionals * gdbstub: DynCom: don't record memory watchpoint hits via RecordBreak() For now, instead check for GDBStub::IsMemoryBreak() in InterpreterMainLoop and ServeBreak. Fixes PC being set to a stale/unhit breakpoint address (often zero) when a memory watchpoint (rwatch, watch, awatch) is handled in ServeBreak() and generates a GDB trap. Reasons for removing a call to RecordBreak() for memory watchpoints: * The``breakpoint_data`` we pass is typed Execute or None. It describes the predicted next code breakpoint hit relative to PC; * GDBStub::IsMemoryBreak() returns true if a recent Read/Write operation hit a watchpoint. It doesn't specify which in return, nor does it trace it anywhere. Thus, the only data we could give RecordBreak() is a placeholder BreakpointAddress at offset NULL and type Access. I found the idea silly, compared to simply relying on GDBStub::IsMemoryBreak(). There is currently no measure in the code that remembers the addresses (and types) of any watchpoints that were hit by an instruction, in order to send them to GDB as "extended stop information." I'm considering an implementation for this. * gdbstub: Change an ASSERT to DEBUG_ASSERT I have never seen the (Reg[15] == last_bkpt.address) assert fail in practice, even after several weeks of (locally) developping various branches around GDB. Only leave it inside Debug builds. |
7 years ago | |
|---|---|---|
| .. | ||
| UtilityFunctions.ps1 | Implement Citra pull 3043 | 8 years ago |