dolphin/Source/Core/Common/BreakPoints.cpp, branch master GameCube and Wii emulator Common: Move BreakPoints into Core 2017-01-10T10:24:44+00:00 Lioncash mathew1800@gmail.com 2016-12-23T19:18:14+00:00 ea8fc594a51785cf7b730df7e91fcf96bafca0ff BreakPoints utilizes the jit global variable, so this was making Core and Common cyclical dependencies on one another. 
BreakPoints utilizes the jit global variable, so this was making Core and
Common cyclical dependencies on one another.
Add the g_ prefix to the jit global 2017-01-07T22:19:49+00:00 Léo Lam leo@innovatetechnologi.es 2017-01-07T22:03:48+00:00 8bef7259e3a12f010bb744a140798aaa3cf17823 Jan 04 22:55:01 <leoetlino> fwiw, it looks like there are new warnings in the RegCache code Jan 04 22:55:04 <leoetlino> Source/Core/Core/PowerPC/Jit64/FPURegCache.cpp:13:33: warning: declaration shadows a variable in the global namespace [-Wshadow] Jan 04 22:56:19 <@Lioncash> yeah, the jit global should have a g_ prefix. This fixes shadowing warnings and adds the g_ prefix to a global. 
Jan 04 22:55:01 <leoetlino>   fwiw, it looks like there are new warnings in the RegCache code
Jan 04 22:55:04 <leoetlino>   Source/Core/Core/PowerPC/Jit64/FPURegCache.cpp:13:33: warning: declaration shadows a variable in the global namespace [-Wshadow]
Jan 04 22:56:19 <@Lioncash>   yeah, the jit global should have a g_ prefix.

This fixes shadowing warnings and adds the g_ prefix to a global.
Merge pull request #4354 from sepalani/bp_rmtmp_it 2016-10-17T21:14:10+00:00 shuffle2 godisgovernment@gmail.com 2016-10-17T21:14:10+00:00 43169d897f091e3b1602372241388a2e24eef8f6 BreakPoints: ClearAllTemporary uses valid iterators 
BreakPoints: ClearAllTemporary uses valid iterators
 BreakPoints: ClearAllTemporary uses valid iterators 2016-10-15T18:21:41+00:00 Sepalani sepalani@hotmail.fr 2016-10-15T17:51:49+00:00 771fa943dc772541f62f6454720690290bb017e1 






Label debugger memchecks as "Memory Breakpoints" in the GUI
2016-10-06T14:51:43+00:00

aldelaro5
aldelaro5@gmail.com

2016-10-06T14:46:09+00:00

549060c5b4c1e28a871930680d4ecc75d75520c5

This is done to remove confusions among potential debugger users and to also make it more accurately tell what this feature is actually doing.  Despite being true that it is using a memcheck (and it certianly checks that memory), the idea being to break on a memory access isn't really obvious especially considering that memchecks are also used in full MMU emulation to handle exceptions.  It also doesn't help that memchecks are now supported in every builds.

It also changes the corresponding log because this log would be wanted by the user which means it should be more obvious that it was caused by the "memory breakpoint".





This is done to remove confusions among potential debugger users and to also make it more accurately tell what this feature is actually doing.  Despite being true that it is using a memcheck (and it certianly checks that memory), the idea being to break on a memory access isn't really obvious especially considering that memchecks are also used in full MMU emulation to handle exceptions.  It also doesn't help that memchecks are now supported in every builds.

It also changes the corresponding log because this log would be wanted by the user which means it should be more obvious that it was caused by the "memory breakpoint".







Merge pull request #4245 from aldelaro5/logs-levels-changes
2016-10-02T20:51:44+00:00

Mat M
mathew1800@gmail.com

2016-10-02T20:51:44+00:00

ccfc0816974bde303ac62bfad019a41ff6fb13f0

Lots of Logs levels changes (also enable INFO level in every build)




Lots of Logs levels changes (also enable INFO level in every build)






Reorganise a ton of logs level
2016-10-01T19:50:28+00:00

aldelaro5
aldelaro5@gmail.com

2016-09-24T23:06:47+00:00

f0aa9b3751f4c3efeb3b1794991533d3d4616d03

Most of this commits changes performance decreasing logs from info to debug and also cleans up innacurate levels.





Most of this commits changes performance decreasing logs from info to debug and also cleans up innacurate levels.







Add consideration for the break flag of memChecks
2016-09-27T05:22:23+00:00

aldelaro5
aldelaro5@gmail.com

2016-09-24T01:15:35+00:00

5e8fc4ebd989b9e59cd670a071fd8a2e2f3d6ba6

It was never used, even when the code tried to make sure it was initialised and passed correctly.  This is a supplementary fix for the memCheck dialog as this option will now work correctly.





It was never used, even when the code tried to make sure it was initialised and passed correctly.  This is a supplementary fix for the memCheck dialog as this option will now work correctly.







Schedule an event to clear the jit cache when adding the first and last
2016-08-21T04:57:35+00:00

aldelaro5
aldelaro5@localhost.localdomain

2016-08-21T03:59:18+00:00

a39e331aad4a110602205a0df2ac084a1b43bf94

memory check

Also fix an oddity in the case when the last memory check is deleted,
the jit cache was supposed to be cleared in that case, but it was out of
the for loop that finds the one to delete so it was never run.
Naturally, the same fix for the adding the first memory check was
applied.





memory check

Also fix an oddity in the case when the last memory check is deleted,
the jit cache was supposed to be cleared in that case, but it was out of
the for loop that finds the one to delete so it was never run.
Naturally, the same fix for the adding the first memory check was
applied.







Reformat all the things. Have fun with merge conflicts.
2016-06-24T08:43:46+00:00

Pierre Bourdon
delroth@gmail.com

2016-06-24T08:43:46+00:00

3570c7f03a2aa90aa634f96c0af1969af610f14d