Downloads & Free Reading Options - Results

“Religion, Violence, Memory, And Place” Metadata:

• Title: ➤  Religion, Violence, Memory, And Place
• Language: English

“Religion, Violence, Memory, And Place” Subjects and Themes:

• Subjects: Memory - Religion - Violence - Place (Philosophy)

Edition Identifiers:

• Internet Archive ID: religionviolence0000unse_w0y6

“Place And Memory - Excavations At The Pict's Knowe, Holywood And Holm Farm, Dumfries And Galloway, 1994-8” Metadata:

• Title: ➤  Place And Memory - Excavations At The Pict's Knowe, Holywood And Holm Farm, Dumfries And Galloway, 1994-8
• Language: English

“Place And Memory - Excavations At The Pict's Knowe, Holywood And Holm Farm, Dumfries And Galloway, 1994-8” Subjects and Themes:

• Subjects: Social Science - Archaeology - book

Edition Identifiers:

• Internet Archive ID: oapen-20.500.12657-53461

“The Chromium Logo The Chromium Projects Home Chromium ChromiumOS Quick Links Report Bugs Discuss Other Sites Chromium Blog Google Chrome Extensions Except As Otherwise Noted, The Content Of This Page Is Licensed Under A Creative Commons Attribution 2.5 License, And Examples Are Licensed Under The BSD License. Privacy Edit This Page For Developers > How-Tos > Debugging Chromium On Windows First See Get The Code For Checkout And Build Instructions. Getting Started You Can Use Visual Studio's Built-in Debugger Or WinDBG To Debug Chromium. You Don't Need To Use The IDE To Build In Order To Use The Debugger: Autoninja Is Used To Build Chromium And Most Developers Invoke It From A Command Prompt, And Then Open The IDE For Debugging As Necessary. To Start Debugging An Already-built Executable With Visual Studio Just Launch Visual Studio (2019 Or Higher) And Select File-> Open-> Project/Solution (Ctrl+Shift+O) And Select The Executable Of Interest. This Will Create A Solution With That Executable As The 'project'. You Can Then Launch The Debugger With F5 Or F11 Or From The Debug Menu. If You Right-click On The Executable In Solution Explorer And Select Properties Then You Can Edit Things Such As The Executable Path, Command-line Arguments, And Working Directory. You Can Add Additional Executables To The Solution By Using File-> Add-> Existing Project And Selecting Another Already-built Executable. You Can Select Which One To Debug By Right-clicking On One Of Them In Solution Explorer And Selecting Set As Startup Project. When Your Solution File Is Customized To Your Taste You Can Save It To A Directory Such As Out\solutions. Saving It There Helps Ensure That Relative Paths To Source Files, Printed From Build Commands, Will Correctly Identify The Source Files. The Tools Menu Can Be Used To Add Commands To Do Things Like Invoke Autoninja To Build Chrome, Compile The Selected Source File, Or Other Things. Visual Studio 2017 Is Not Recommended For Debugging Of Chromium - Use A Newer Version For Best Performance And Stability. Symbol_level=2 Is The Default On Windows And Gives Full Debugging Information With Types, Locals, Globals, Function Names, And Source/line Information. Symbol_level=1 Creates Smaller PDBs With Just Function Names, And Source/line Information - Source-level Debugging Is Still Supported (new From June 2019), But Local Variables And Type Information Are Missing. Symbol_level=0 Gives Extremely Limited Debugging Abilities, Mostly Just Viewing Call Stacks When Chromium Crashes. Browsing Source Code If You Use A Solution File Generated By Gn (gn Gen --ide=vs) Then Intellisense May Help You Navigate The Code. If This Doesn't Work Or If You Use A Solution Created As Above Then You May Want To Install VsChromium To Help Navigate The Code, As Well As Using Https://source.chromium.org. Profiles It's A Good Idea To Use A Different Chrome Profile For Your Debugging. If You Are Debugging Google Chrome Branded Builds, Or Use A Chromium Build As Your Primary Browser, The Profiles Can Collide So You Can't Run Both At Once, And Your Stable Browser Might See Profile Versions From The Future (Google Chrome And Chromium Use Different Profile Directories By Default So Won't Collide). Use The Command-line Option: --user-data-dir=C:\tmp\my_debug_profile (replace The Path As Necessary) Using The IDE, Go To The Debugging Tab Of The Properties Of The Chrome Project, And Set The Command Arguments. Chrome Debug Log Enable Chrome Debug Logging To A File By Passing --enable-logging --v=1 Command-line Flags At Startup. Debug Builds Place The Chrome_debug.log File In The Out\Debug Directory. Release Builds Place The File In The Top Level Of The User Data Chromium App Directory, Which Is OS-version-dependent. For More Information, See Logging And User Data Directory Details. Symbol Server If You Are Debugging Official Google Chrome Release Builds, Use The Symbol Server: Https://chromium-browser-symsrv.commondatastorage.googleapis.com In Visual Studio, This Goes In Tools > Options Under Debugging > Symbols. You Should Set Up A Local Cache In A Empty Directory On Your Computer. In Windbg You Can Add This To Your Symbol Server Search Path With The Command Below, Where C:\symbols Is A Local Cache Directory: .sympath+ SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Alternately, You Can Set The _NT_SYMBOL_PATH Environment Variable To Include Both The Microsoft And Google Symbol Servers - VS, Windbg, And Other Tools Should Both Respect This Environment Variable: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Note That Symbol Servers Will Let The Debuggers Download Both The PE Files (DLLs And EXEs) And The PDB Files. Chrome Often Loads Third Party Libraries And Partial Symbols For Some Of These Are Also Public. For Example: AMD: Https://download.amd.com/dir/bin Nvidia: Https://driver-symbols.nvidia.com/ Intel: Https://software.intel.com/sites/downloads/symbols/ For Example, For Completeness, The Following Symbol Server Environment Variable Will Resolve All Of The Above Sources - But This Is More Than Is Normally Needed: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com;SRV\*C:\symbols\*https://download.amd.com/dir/bin;SRV\*C:\symbols\*https://driver-symbols.nvidia.com/;SRV\*C:\symbols\*https://software.intel.com/sites/downloads/symbols/ Source Indexing You Should Set Up Source Indexing In Your Debugger (.srcfix In Windbg, Tools-> Options-> Debugging-> General-> Enable Source Server Support In Visual Studio) So That The Correct Source Files Will Automatically Be Downloaded Based On Information In The Downloaded Symbols. Additionally, You Must Have Python In Your Path In Order For The Command That Fetches Source Files To Succeed; Launching The Debugger From The Same Environment As Where You Build Chromium Is An Easy Way To Ensure It's Present. This Is Highly Recommended When Debugging Released Google Chrome Builds Or Looking At Crash Dumps. Having The Correct Version Of The Source Files Automatically Show Up Saves Significant Time So You Should Definitely Set This. Multi-process Issues Chromium Can Be Challenging To Debug Because Of Its Multi-process Architecture. When You Select Run In The Debugger, Only The Main Browser Process Will Be Debugged. The Code That Actually Renders Web Pages (the Renderer) And The Plugins Will Be In Separate Processes That's Not (yet!) Being Debugged. The ProcessExplorer Tool Has A Process Tree View Where You Can See How These Processes Are Related. You Can Also Get The Process IDs Associated With Each Tab From The Chrome Task Manager (right-click On An Empty Area Of The Window Title Bar To Open). Automatically Attach To Child Processes There Are Two Visual Studio Extensions That Enable The Debugger To Automatically Attach To All Chrome Processes, So You Can Debug All Of Chrome At Once. Microsoft's Child Process Debugging Power Tool Is A Standalone Extension For This, And VsChromium Is Another Option That Bundles Many Other Additional Features. In Addition To Installing One Of These Extensions, You Must Run Visual Studio As Administrator, Or It Will Silently Fail To Attach To Some Of Chrome's Child Processes. Single-process Mode One Way To Debug Issues Is To Run Chromium In Single-process Mode. This Will Allow You To See The Entire State Of The Program Without Extra Work (although It Will Still Have Many Threads). To Use Single-process Mode, Add The Command-line Flag --single-process This Approach Isn't Perfect Because Some Problems Won't Manifest Themselves In This Mode And Some Features Don't Work And Worker Threads Are Still Spawned Into New Processes. Manually Attaching To A Child Process You Can Attach To The Running Child Processes With The Debugger. Select Tools > Attach To Process And Click The Chrome.exe Process You Want To Attach To. Before Attaching, Make Sure You Have Selected Only Native Code When Attaching To The Process This Is Done By Clicking Select... In The Attach To Process Window And Only Checking Native. If You Forget This, It May Attempt To Attach In "WebKit" Mode To Debug JavaScript, And You'll Get An Error Message "An Operation Is Not Legal In The Current State." You Can Now Debug The Two Processes As If They Were One. When You Are Debugging Multiple Processes, Open The Debug > Windows > Processes Window To Switch Between Them. Sometimes You Are Debugging Something That Only Happens On Startup, And Want To See The Child Process As Soon As It Starts. Use: --renderer-startup-dialog --no-sandbox You Have To Disable The Sandbox Or The Dialog Box Will Be Prohibited From Showing. When The Dialog Appears, Visit Tools > Attach To Process And Attach To The Process Showing The Renderer Startup Dialog. Now You're Debugging In The Renderer And Can Continue Execution By Pressing OK In The Dialog. Startup Dialogs Also Exist For Other Child Process Types: --gpu-startup-dialog, --ppapi-startup-dialog, --utility-startup-dialog, --plugin-startup-dialog (for NPAPI). For Utilities, You Can Add A Service Type --utility-startup-dialog=data_decoder.mojom.DataDecoderService. You Can Also Try The Vs-chromium Plug-in To Attach To The Right Processes. Semi-automatically Attaching The Debugger To Child Processes The Following Flags Cause Child Processes To Wait For 60 Seconds In A Busy Loop For A Debugger To Attach To The Process. Once Either Condition Is True, It Continues On; No Exception Is Thrown. --wait-for-debugger-children[=filter] The Filter, If Provided, Will Fire Only If It Matches The --type Parameter To The Process. Values Include Renderer, Plugin (for NPAPI), Ppapi, Gpu-process, And Utility. When Using This Option, It May Be Helpful To Limit The Number Of Renderer Processes Spawned, Using: --renderer-process-limit=1 Image File Execution Options Using Image File Execution Options (IFEO) Will Not Work Because CreateProcess() Returns The Handle To The Debugger Process Instead Of The Intended Child Process. There Are Also Issues With The Sandbox. Time Travel Debugging You Can Do Time Travel Debugging Using WinDbg Preview (must Be Installed From The Microsoft Store). This Lets You Execute A Program Forward And Backwards. After Capturing A Trace, You Can Set Breakpoints And Step Through Code As Normal, But Also Provides 'backwards' Commands (g-, T-, P-) So That You Can Go Back And Forth Through The Execution. It Is Especially Useful To Set Data Breakpoints (ba Command) And Reverse Continuing, So You Can See When A Certain Variable Was Last Changed To Its Current Value. Chromium Specifics: The Type Of Injection The Time Travel Tracer Needs To Perform Is Incompatible With The Chromium Sandbox. In Order To Record A Trace, You'll Need To Run With --no-sandbox. Chromium Cannot Run Elevated With Administrator Privileges, So The "Launch Executable (advance)" Option Won't Work, You'll Need To Attach After The Process Has Already Launched Via The Checkbox In The Bottom Right. If You Need To Record Startup-like Things, You'll Have To Use --{browser,gpu,renderer,utility}-startup-dialog, Then Attach (and Hope The Relevant Code Hasn't Executed Before That Point). JsDbg -- Data Structure Visualization You Can Install JsDbg As A Plugin For WinDbg Or Visual Studio. It Interactively Lets You Look At Data Structures (such As The DOM Tree, Accessibility Tree, Layout Object Tree, And Others) In A Web Browser As You Debug. See The JsDbg Site For Some Screen Shots And Usage Examples. This Also Works When Examining Memory Dumps (though Not Minidumps), And Also Works Together With Time Travel Debugging. Visual Studio Hints Debug Visualizers Chrome's Custom Debug Visualizers Should Be Added To The Pdb Files And Automatically Picked Up By Visual Studio. The Definitions Are In //tools/win/DebugVisualizers If You Need To Modify Them (the BUILD.gn File There Has Additional Instructions). Don't Step Into Trivial Functions The Debugger Can Be Configured To Automatically Not Step Into Functions Based On Regular Expression. Edit Default.natstepfilter In The Following Directory: For Visual Studio 2015: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2015\Visualizers (for The Current User Only) For Visual Studio 2017 Pro: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2017\Visualizers (for The Current User Only) Add Regular Expressions Of Functions To Not Step Into. Remember To Regex-escape And XML-escape Them, E.g. < For < And \. For A Literal Dot. Example: Operator New NoStepInto Operator Delete NoStepInto Std::.* NoStepInto WTF::.*Ptr ::.* NoStepInto This File Is Read At Start Of A Debugging Session (F5), So You Don't Need To Restart Visual Studio After Changing It. More Info: Microsoft Email Thread V8 And Chromium V8 Supports Many Command-line Flags That Are Useful For Debugging. V8 Command-line Flags Can Be Set Via The Chromium Command-line Flag --js-flags; For Instance: Chrome.exe --js-flags="--trace_exception --heap_stats" Note That Some V8 Command-line Flags Exist Only In The Debug Build Of V8. For A List Of All V8 Flags Try: Chrome.exe --js-flags="--help" Graphics Debugging GPU Acceleration Of Rendering Can Be More Easily Debugged With Tools. See: Graphics Debugging In Visual Studio 2013 Graphical Debugging With NVIDIA NSight Debugging On Another Machine Sometimes It's Useful To Debug Installation And Execution On A Machine Other Than Your Primary Build Box. To Run The Installer On Said Other Machine, First Build The Mini_installer Target On Your Main Build Machine (e.g., Autoninja -C Out\Debug Mini_installer). Next, On The Debug Machine: Make The Build Machine's Build Volume Available On The Debug Machine Either By Mounting It Locally (e.g., Z:\) Or By Crafting A UNC Path To It (e.g., \\builder\src) Open Up A Command Prompt And Change To A Local Disk Run Src\tools\win\copy-installer.bat In The Remote Checkout By Way Of The Mount (e.g., Z:\PATHTOCHECKOUT\src\...) Or UNC Path (e.g., \\builder\src\...). This Will Copy The Installer, DLLs, And PDBs Into Your Debug Machine's C:\out Or C:\build (depending On If You're Rocking The Component=shared_library Build Or Not) Run C:\out\Debug\mini_installer.exe With The Flags Of Your Choice To Install Chrome. This Can Take Some Time, Especially On A Slow Machine. Watch The Task Manager And Wait Until Mini_installer.exe Exits Before Trying To Launch Chrome (by Way Of The Shortcut(s) Created By The Installer) For Extra Pleasure, Add C:\out\Debug To Your _NT_SYMBOL_PATH Environment Variable Consider Reading The Documentation At The Top Of Copy-installer.bat To See How You Can Run It. It Tries To Be Smart And Copy The Right Things, But You May Need To Be Explicit (e.g., "copy-installer.bat Out Debug"). It Is Safe To Re-run The Script To Copy Only Modified Files (after A Rebuild, For Example). You Can Also Use The Zip Action Of The Isolate Scripts (tools\mb\mb.py) To Package All The Files For A Target Into A Single Zip File, For Example: Python Tools\mb\mb.py Zip Out/Release Base_unittests Base_unittests.zip Finding All Memory Allocations It Is Possible To Use Heap Snapshots To Get Call Stacks On All Outstanding Allocations That Use The OS Heap. This Works Particularly Well If Heap Snapshots Are Started As Soon As The Chrome Browser Process Is Created, But Before It Starts Running. Details Can Be Found In This Batch File. However, With PartitionAlloc Everywhere Most Chromium Allocations No Longer Use The Windows Heap So This Will Only Find A Subset Of Allocations, Mostly From OS DLLs. Find Memory Leaks Note: As With Heap Snapshots The Utility Of UMDH Is Greatly Reduced Now Because PartitionAlloc Everywhere Has Mostly Replaced The Windows Heap. The Windows Heap Manager Has A Really Useful Debug Flag, Where It Can Be Asked To Capture And Store A Stack Trace With Every Allocation. The Tool To Scrape These Stack Traces Out Of Processes Is UMDH, Which Comes With WinDbg. UMDH Is Great. It Will Capture A Snapshot Of The Heap State As Many Times As You Like, And It'll Do It Fairly Quickly. You Then Run It Again Against Either A Single Snapshot, Or A Pair Of Snapshots, At Which Time It'll Symbolize The Stack Traces And Aggregate Usage Up To Unique Stack Traces. Turning On The User Stack Trace Database For Chrome.exe With Gflags.exe Makes It Run Unbearably Slowly; However, Turning On The User Stack Trace Database On For The Browser Alone Is Just Fine. While It's Possible To Turn On The User Stack Database With The "!gflag" Debugging Extension, It's Too Late To Do This By The Time The Initial Debugger Breakpoint Hits. The Only Reasonable Way To Do This Is To Launch GFlags.exe, Enable The User Stack Trace Database (per Image Below), Launch Chrome Under The Debugger. Set A Breakpont When Chrome.dll Loads With "sxe Ld Chrome.dll". Step Up, To Allow Chrome.dll To Initialize. Disable The Stack Trace Database In GFlags.exe. Continue Chrome, Optionally Detaching The Debugger. Image GFlags.exe Settings For User Mode Stack Trace Database. If You Then Ever Suffer A Browser Memory Leak, You Can Snarf A Dump Of The Process With Umdh -p: > Chrome-browser-leak-umdh-dump.txt Which Can Then Typically Be "trivially" Analyzed To Find The Culprit. Miscellaneous Note That By Default Application Verifier Only Works With Non-official Builds Of Chromium. To Use Application Verifier On Official Builds You Need To Add --disable-features=RendererCodeIntegrity To Avoid Sandbox Crashes In Renderer Processes. See Crbug.com/1004989 For Details. See Also This Page. Application Verifier Is A Free Tool From Microsoft (available As Part Of The Windows SDK) That Can Be Used To Flush Out Programming Errors. Starting With M68 Application Verifier Can Be Enabled For Chrome.exe Without Needing To Disable The Sandbox. After Adding Chrome.exe To The List Of Applications To Be Stressed You Need To Expand The List Of Basics Checks And Disable The Leak Checks. You May Also Need To Disable Handles And Locks Checks Depending On Your Graphics Driver And Specific Chrome Version, But The Eventual Goal Is To Have Chrome Run With Handles And Locks Checks Enabled. When Bugs Are Found Chrome Will Trigger A Breakpoint So Running All Chrome Processes Under A Debugger Is Recommended. Chrome Will Run Much More Slowly Because Application Verifier Puts Every Heap Allocation On A Separate Page. Note That With PartitionAlloc Everywhere Most Chromium Allocations Don't Actually Go Through The Windows Heap And Are Therefore Unaffected By Application Verifier. You Can Check The Undocumented 'Cuzz' Checkbox In Application Verifier To Get The Windows Thread Scheduler To Add Some Extra Randomness In Order To Help Expose Race Conditions In Your Code. To Put A Breakpoint On CreateFile(), Add This Break Point: {,,kernel32.dll}_CreateFileW@28 {,,kernel32.dll} Specifies The DLL (context Operator). _ Prefix Means Extern "C". @28 Postfix Means _stdcall With The Stack Pop At The End Of The Function. I.e. The Number Of Arguments In BYTES. You Can Use DebugView From SysInternals Or Sawbuck To View LOG() Messages That Normally Go To Stderr On POSIX.” Metadata:

• Title: ➤  The Chromium Logo The Chromium Projects Home Chromium ChromiumOS Quick Links Report Bugs Discuss Other Sites Chromium Blog Google Chrome Extensions Except As Otherwise Noted, The Content Of This Page Is Licensed Under A Creative Commons Attribution 2.5 License, And Examples Are Licensed Under The BSD License. Privacy Edit This Page For Developers > How-Tos > Debugging Chromium On Windows First See Get The Code For Checkout And Build Instructions. Getting Started You Can Use Visual Studio's Built-in Debugger Or WinDBG To Debug Chromium. You Don't Need To Use The IDE To Build In Order To Use The Debugger: Autoninja Is Used To Build Chromium And Most Developers Invoke It From A Command Prompt, And Then Open The IDE For Debugging As Necessary. To Start Debugging An Already-built Executable With Visual Studio Just Launch Visual Studio (2019 Or Higher) And Select File-> Open-> Project/Solution (Ctrl+Shift+O) And Select The Executable Of Interest. This Will Create A Solution With That Executable As The 'project'. You Can Then Launch The Debugger With F5 Or F11 Or From The Debug Menu. If You Right-click On The Executable In Solution Explorer And Select Properties Then You Can Edit Things Such As The Executable Path, Command-line Arguments, And Working Directory. You Can Add Additional Executables To The Solution By Using File-> Add-> Existing Project And Selecting Another Already-built Executable. You Can Select Which One To Debug By Right-clicking On One Of Them In Solution Explorer And Selecting Set As Startup Project. When Your Solution File Is Customized To Your Taste You Can Save It To A Directory Such As Out\solutions. Saving It There Helps Ensure That Relative Paths To Source Files, Printed From Build Commands, Will Correctly Identify The Source Files. The Tools Menu Can Be Used To Add Commands To Do Things Like Invoke Autoninja To Build Chrome, Compile The Selected Source File, Or Other Things. Visual Studio 2017 Is Not Recommended For Debugging Of Chromium - Use A Newer Version For Best Performance And Stability. Symbol_level=2 Is The Default On Windows And Gives Full Debugging Information With Types, Locals, Globals, Function Names, And Source/line Information. Symbol_level=1 Creates Smaller PDBs With Just Function Names, And Source/line Information - Source-level Debugging Is Still Supported (new From June 2019), But Local Variables And Type Information Are Missing. Symbol_level=0 Gives Extremely Limited Debugging Abilities, Mostly Just Viewing Call Stacks When Chromium Crashes. Browsing Source Code If You Use A Solution File Generated By Gn (gn Gen --ide=vs) Then Intellisense May Help You Navigate The Code. If This Doesn't Work Or If You Use A Solution Created As Above Then You May Want To Install VsChromium To Help Navigate The Code, As Well As Using Https://source.chromium.org. Profiles It's A Good Idea To Use A Different Chrome Profile For Your Debugging. If You Are Debugging Google Chrome Branded Builds, Or Use A Chromium Build As Your Primary Browser, The Profiles Can Collide So You Can't Run Both At Once, And Your Stable Browser Might See Profile Versions From The Future (Google Chrome And Chromium Use Different Profile Directories By Default So Won't Collide). Use The Command-line Option: --user-data-dir=C:\tmp\my_debug_profile (replace The Path As Necessary) Using The IDE, Go To The Debugging Tab Of The Properties Of The Chrome Project, And Set The Command Arguments. Chrome Debug Log Enable Chrome Debug Logging To A File By Passing --enable-logging --v=1 Command-line Flags At Startup. Debug Builds Place The Chrome_debug.log File In The Out\Debug Directory. Release Builds Place The File In The Top Level Of The User Data Chromium App Directory, Which Is OS-version-dependent. For More Information, See Logging And User Data Directory Details. Symbol Server If You Are Debugging Official Google Chrome Release Builds, Use The Symbol Server: Https://chromium-browser-symsrv.commondatastorage.googleapis.com In Visual Studio, This Goes In Tools > Options Under Debugging > Symbols. You Should Set Up A Local Cache In A Empty Directory On Your Computer. In Windbg You Can Add This To Your Symbol Server Search Path With The Command Below, Where C:\symbols Is A Local Cache Directory: .sympath+ SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Alternately, You Can Set The _NT_SYMBOL_PATH Environment Variable To Include Both The Microsoft And Google Symbol Servers - VS, Windbg, And Other Tools Should Both Respect This Environment Variable: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Note That Symbol Servers Will Let The Debuggers Download Both The PE Files (DLLs And EXEs) And The PDB Files. Chrome Often Loads Third Party Libraries And Partial Symbols For Some Of These Are Also Public. For Example: AMD: Https://download.amd.com/dir/bin Nvidia: Https://driver-symbols.nvidia.com/ Intel: Https://software.intel.com/sites/downloads/symbols/ For Example, For Completeness, The Following Symbol Server Environment Variable Will Resolve All Of The Above Sources - But This Is More Than Is Normally Needed: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com;SRV\*C:\symbols\*https://download.amd.com/dir/bin;SRV\*C:\symbols\*https://driver-symbols.nvidia.com/;SRV\*C:\symbols\*https://software.intel.com/sites/downloads/symbols/ Source Indexing You Should Set Up Source Indexing In Your Debugger (.srcfix In Windbg, Tools-> Options-> Debugging-> General-> Enable Source Server Support In Visual Studio) So That The Correct Source Files Will Automatically Be Downloaded Based On Information In The Downloaded Symbols. Additionally, You Must Have Python In Your Path In Order For The Command That Fetches Source Files To Succeed; Launching The Debugger From The Same Environment As Where You Build Chromium Is An Easy Way To Ensure It's Present. This Is Highly Recommended When Debugging Released Google Chrome Builds Or Looking At Crash Dumps. Having The Correct Version Of The Source Files Automatically Show Up Saves Significant Time So You Should Definitely Set This. Multi-process Issues Chromium Can Be Challenging To Debug Because Of Its Multi-process Architecture. When You Select Run In The Debugger, Only The Main Browser Process Will Be Debugged. The Code That Actually Renders Web Pages (the Renderer) And The Plugins Will Be In Separate Processes That's Not (yet!) Being Debugged. The ProcessExplorer Tool Has A Process Tree View Where You Can See How These Processes Are Related. You Can Also Get The Process IDs Associated With Each Tab From The Chrome Task Manager (right-click On An Empty Area Of The Window Title Bar To Open). Automatically Attach To Child Processes There Are Two Visual Studio Extensions That Enable The Debugger To Automatically Attach To All Chrome Processes, So You Can Debug All Of Chrome At Once. Microsoft's Child Process Debugging Power Tool Is A Standalone Extension For This, And VsChromium Is Another Option That Bundles Many Other Additional Features. In Addition To Installing One Of These Extensions, You Must Run Visual Studio As Administrator, Or It Will Silently Fail To Attach To Some Of Chrome's Child Processes. Single-process Mode One Way To Debug Issues Is To Run Chromium In Single-process Mode. This Will Allow You To See The Entire State Of The Program Without Extra Work (although It Will Still Have Many Threads). To Use Single-process Mode, Add The Command-line Flag --single-process This Approach Isn't Perfect Because Some Problems Won't Manifest Themselves In This Mode And Some Features Don't Work And Worker Threads Are Still Spawned Into New Processes. Manually Attaching To A Child Process You Can Attach To The Running Child Processes With The Debugger. Select Tools > Attach To Process And Click The Chrome.exe Process You Want To Attach To. Before Attaching, Make Sure You Have Selected Only Native Code When Attaching To The Process This Is Done By Clicking Select... In The Attach To Process Window And Only Checking Native. If You Forget This, It May Attempt To Attach In "WebKit" Mode To Debug JavaScript, And You'll Get An Error Message "An Operation Is Not Legal In The Current State." You Can Now Debug The Two Processes As If They Were One. When You Are Debugging Multiple Processes, Open The Debug > Windows > Processes Window To Switch Between Them. Sometimes You Are Debugging Something That Only Happens On Startup, And Want To See The Child Process As Soon As It Starts. Use: --renderer-startup-dialog --no-sandbox You Have To Disable The Sandbox Or The Dialog Box Will Be Prohibited From Showing. When The Dialog Appears, Visit Tools > Attach To Process And Attach To The Process Showing The Renderer Startup Dialog. Now You're Debugging In The Renderer And Can Continue Execution By Pressing OK In The Dialog. Startup Dialogs Also Exist For Other Child Process Types: --gpu-startup-dialog, --ppapi-startup-dialog, --utility-startup-dialog, --plugin-startup-dialog (for NPAPI). For Utilities, You Can Add A Service Type --utility-startup-dialog=data_decoder.mojom.DataDecoderService. You Can Also Try The Vs-chromium Plug-in To Attach To The Right Processes. Semi-automatically Attaching The Debugger To Child Processes The Following Flags Cause Child Processes To Wait For 60 Seconds In A Busy Loop For A Debugger To Attach To The Process. Once Either Condition Is True, It Continues On; No Exception Is Thrown. --wait-for-debugger-children[=filter] The Filter, If Provided, Will Fire Only If It Matches The --type Parameter To The Process. Values Include Renderer, Plugin (for NPAPI), Ppapi, Gpu-process, And Utility. When Using This Option, It May Be Helpful To Limit The Number Of Renderer Processes Spawned, Using: --renderer-process-limit=1 Image File Execution Options Using Image File Execution Options (IFEO) Will Not Work Because CreateProcess() Returns The Handle To The Debugger Process Instead Of The Intended Child Process. There Are Also Issues With The Sandbox. Time Travel Debugging You Can Do Time Travel Debugging Using WinDbg Preview (must Be Installed From The Microsoft Store). This Lets You Execute A Program Forward And Backwards. After Capturing A Trace, You Can Set Breakpoints And Step Through Code As Normal, But Also Provides 'backwards' Commands (g-, T-, P-) So That You Can Go Back And Forth Through The Execution. It Is Especially Useful To Set Data Breakpoints (ba Command) And Reverse Continuing, So You Can See When A Certain Variable Was Last Changed To Its Current Value. Chromium Specifics: The Type Of Injection The Time Travel Tracer Needs To Perform Is Incompatible With The Chromium Sandbox. In Order To Record A Trace, You'll Need To Run With --no-sandbox. Chromium Cannot Run Elevated With Administrator Privileges, So The "Launch Executable (advance)" Option Won't Work, You'll Need To Attach After The Process Has Already Launched Via The Checkbox In The Bottom Right. If You Need To Record Startup-like Things, You'll Have To Use --{browser,gpu,renderer,utility}-startup-dialog, Then Attach (and Hope The Relevant Code Hasn't Executed Before That Point). JsDbg -- Data Structure Visualization You Can Install JsDbg As A Plugin For WinDbg Or Visual Studio. It Interactively Lets You Look At Data Structures (such As The DOM Tree, Accessibility Tree, Layout Object Tree, And Others) In A Web Browser As You Debug. See The JsDbg Site For Some Screen Shots And Usage Examples. This Also Works When Examining Memory Dumps (though Not Minidumps), And Also Works Together With Time Travel Debugging. Visual Studio Hints Debug Visualizers Chrome's Custom Debug Visualizers Should Be Added To The Pdb Files And Automatically Picked Up By Visual Studio. The Definitions Are In //tools/win/DebugVisualizers If You Need To Modify Them (the BUILD.gn File There Has Additional Instructions). Don't Step Into Trivial Functions The Debugger Can Be Configured To Automatically Not Step Into Functions Based On Regular Expression. Edit Default.natstepfilter In The Following Directory: For Visual Studio 2015: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2015\Visualizers (for The Current User Only) For Visual Studio 2017 Pro: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2017\Visualizers (for The Current User Only) Add Regular Expressions Of Functions To Not Step Into. Remember To Regex-escape And XML-escape Them, E.g. < For < And \. For A Literal Dot. Example: Operator New NoStepInto Operator Delete NoStepInto Std::.* NoStepInto WTF::.*Ptr ::.* NoStepInto This File Is Read At Start Of A Debugging Session (F5), So You Don't Need To Restart Visual Studio After Changing It. More Info: Microsoft Email Thread V8 And Chromium V8 Supports Many Command-line Flags That Are Useful For Debugging. V8 Command-line Flags Can Be Set Via The Chromium Command-line Flag --js-flags; For Instance: Chrome.exe --js-flags="--trace_exception --heap_stats" Note That Some V8 Command-line Flags Exist Only In The Debug Build Of V8. For A List Of All V8 Flags Try: Chrome.exe --js-flags="--help" Graphics Debugging GPU Acceleration Of Rendering Can Be More Easily Debugged With Tools. See: Graphics Debugging In Visual Studio 2013 Graphical Debugging With NVIDIA NSight Debugging On Another Machine Sometimes It's Useful To Debug Installation And Execution On A Machine Other Than Your Primary Build Box. To Run The Installer On Said Other Machine, First Build The Mini_installer Target On Your Main Build Machine (e.g., Autoninja -C Out\Debug Mini_installer). Next, On The Debug Machine: Make The Build Machine's Build Volume Available On The Debug Machine Either By Mounting It Locally (e.g., Z:\) Or By Crafting A UNC Path To It (e.g., \\builder\src) Open Up A Command Prompt And Change To A Local Disk Run Src\tools\win\copy-installer.bat In The Remote Checkout By Way Of The Mount (e.g., Z:\PATHTOCHECKOUT\src\...) Or UNC Path (e.g., \\builder\src\...). This Will Copy The Installer, DLLs, And PDBs Into Your Debug Machine's C:\out Or C:\build (depending On If You're Rocking The Component=shared_library Build Or Not) Run C:\out\Debug\mini_installer.exe With The Flags Of Your Choice To Install Chrome. This Can Take Some Time, Especially On A Slow Machine. Watch The Task Manager And Wait Until Mini_installer.exe Exits Before Trying To Launch Chrome (by Way Of The Shortcut(s) Created By The Installer) For Extra Pleasure, Add C:\out\Debug To Your _NT_SYMBOL_PATH Environment Variable Consider Reading The Documentation At The Top Of Copy-installer.bat To See How You Can Run It. It Tries To Be Smart And Copy The Right Things, But You May Need To Be Explicit (e.g., "copy-installer.bat Out Debug"). It Is Safe To Re-run The Script To Copy Only Modified Files (after A Rebuild, For Example). You Can Also Use The Zip Action Of The Isolate Scripts (tools\mb\mb.py) To Package All The Files For A Target Into A Single Zip File, For Example: Python Tools\mb\mb.py Zip Out/Release Base_unittests Base_unittests.zip Finding All Memory Allocations It Is Possible To Use Heap Snapshots To Get Call Stacks On All Outstanding Allocations That Use The OS Heap. This Works Particularly Well If Heap Snapshots Are Started As Soon As The Chrome Browser Process Is Created, But Before It Starts Running. Details Can Be Found In This Batch File. However, With PartitionAlloc Everywhere Most Chromium Allocations No Longer Use The Windows Heap So This Will Only Find A Subset Of Allocations, Mostly From OS DLLs. Find Memory Leaks Note: As With Heap Snapshots The Utility Of UMDH Is Greatly Reduced Now Because PartitionAlloc Everywhere Has Mostly Replaced The Windows Heap. The Windows Heap Manager Has A Really Useful Debug Flag, Where It Can Be Asked To Capture And Store A Stack Trace With Every Allocation. The Tool To Scrape These Stack Traces Out Of Processes Is UMDH, Which Comes With WinDbg. UMDH Is Great. It Will Capture A Snapshot Of The Heap State As Many Times As You Like, And It'll Do It Fairly Quickly. You Then Run It Again Against Either A Single Snapshot, Or A Pair Of Snapshots, At Which Time It'll Symbolize The Stack Traces And Aggregate Usage Up To Unique Stack Traces. Turning On The User Stack Trace Database For Chrome.exe With Gflags.exe Makes It Run Unbearably Slowly; However, Turning On The User Stack Trace Database On For The Browser Alone Is Just Fine. While It's Possible To Turn On The User Stack Database With The "!gflag" Debugging Extension, It's Too Late To Do This By The Time The Initial Debugger Breakpoint Hits. The Only Reasonable Way To Do This Is To Launch GFlags.exe, Enable The User Stack Trace Database (per Image Below), Launch Chrome Under The Debugger. Set A Breakpont When Chrome.dll Loads With "sxe Ld Chrome.dll". Step Up, To Allow Chrome.dll To Initialize. Disable The Stack Trace Database In GFlags.exe. Continue Chrome, Optionally Detaching The Debugger. Image GFlags.exe Settings For User Mode Stack Trace Database. If You Then Ever Suffer A Browser Memory Leak, You Can Snarf A Dump Of The Process With Umdh -p: > Chrome-browser-leak-umdh-dump.txt Which Can Then Typically Be "trivially" Analyzed To Find The Culprit. Miscellaneous Note That By Default Application Verifier Only Works With Non-official Builds Of Chromium. To Use Application Verifier On Official Builds You Need To Add --disable-features=RendererCodeIntegrity To Avoid Sandbox Crashes In Renderer Processes. See Crbug.com/1004989 For Details. See Also This Page. Application Verifier Is A Free Tool From Microsoft (available As Part Of The Windows SDK) That Can Be Used To Flush Out Programming Errors. Starting With M68 Application Verifier Can Be Enabled For Chrome.exe Without Needing To Disable The Sandbox. After Adding Chrome.exe To The List Of Applications To Be Stressed You Need To Expand The List Of Basics Checks And Disable The Leak Checks. You May Also Need To Disable Handles And Locks Checks Depending On Your Graphics Driver And Specific Chrome Version, But The Eventual Goal Is To Have Chrome Run With Handles And Locks Checks Enabled. When Bugs Are Found Chrome Will Trigger A Breakpoint So Running All Chrome Processes Under A Debugger Is Recommended. Chrome Will Run Much More Slowly Because Application Verifier Puts Every Heap Allocation On A Separate Page. Note That With PartitionAlloc Everywhere Most Chromium Allocations Don't Actually Go Through The Windows Heap And Are Therefore Unaffected By Application Verifier. You Can Check The Undocumented 'Cuzz' Checkbox In Application Verifier To Get The Windows Thread Scheduler To Add Some Extra Randomness In Order To Help Expose Race Conditions In Your Code. To Put A Breakpoint On CreateFile(), Add This Break Point: {,,kernel32.dll}_CreateFileW@28 {,,kernel32.dll} Specifies The DLL (context Operator). _ Prefix Means Extern "C". @28 Postfix Means _stdcall With The Stack Pop At The End Of The Function. I.e. The Number Of Arguments In BYTES. You Can Use DebugView From SysInternals Or Sawbuck To View LOG() Messages That Normally Go To Stderr On POSIX.

“The Chromium Logo The Chromium Projects Home Chromium ChromiumOS Quick Links Report Bugs Discuss Other Sites Chromium Blog Google Chrome Extensions Except As Otherwise Noted, The Content Of This Page Is Licensed Under A Creative Commons Attribution 2.5 License, And Examples Are Licensed Under The BSD License. Privacy Edit This Page For Developers > How-Tos > Debugging Chromium On Windows First See Get The Code For Checkout And Build Instructions. Getting Started You Can Use Visual Studio's Built-in Debugger Or WinDBG To Debug Chromium. You Don't Need To Use The IDE To Build In Order To Use The Debugger: Autoninja Is Used To Build Chromium And Most Developers Invoke It From A Command Prompt, And Then Open The IDE For Debugging As Necessary. To Start Debugging An Already-built Executable With Visual Studio Just Launch Visual Studio (2019 Or Higher) And Select File-> Open-> Project/Solution (Ctrl+Shift+O) And Select The Executable Of Interest. This Will Create A Solution With That Executable As The 'project'. You Can Then Launch The Debugger With F5 Or F11 Or From The Debug Menu. If You Right-click On The Executable In Solution Explorer And Select Properties Then You Can Edit Things Such As The Executable Path, Command-line Arguments, And Working Directory. You Can Add Additional Executables To The Solution By Using File-> Add-> Existing Project And Selecting Another Already-built Executable. You Can Select Which One To Debug By Right-clicking On One Of Them In Solution Explorer And Selecting Set As Startup Project. When Your Solution File Is Customized To Your Taste You Can Save It To A Directory Such As Out\solutions. Saving It There Helps Ensure That Relative Paths To Source Files, Printed From Build Commands, Will Correctly Identify The Source Files. The Tools Menu Can Be Used To Add Commands To Do Things Like Invoke Autoninja To Build Chrome, Compile The Selected Source File, Or Other Things. Visual Studio 2017 Is Not Recommended For Debugging Of Chromium - Use A Newer Version For Best Performance And Stability. Symbol_level=2 Is The Default On Windows And Gives Full Debugging Information With Types, Locals, Globals, Function Names, And Source/line Information. Symbol_level=1 Creates Smaller PDBs With Just Function Names, And Source/line Information - Source-level Debugging Is Still Supported (new From June 2019), But Local Variables And Type Information Are Missing. Symbol_level=0 Gives Extremely Limited Debugging Abilities, Mostly Just Viewing Call Stacks When Chromium Crashes. Browsing Source Code If You Use A Solution File Generated By Gn (gn Gen --ide=vs) Then Intellisense May Help You Navigate The Code. If This Doesn't Work Or If You Use A Solution Created As Above Then You May Want To Install VsChromium To Help Navigate The Code, As Well As Using Https://source.chromium.org. Profiles It's A Good Idea To Use A Different Chrome Profile For Your Debugging. If You Are Debugging Google Chrome Branded Builds, Or Use A Chromium Build As Your Primary Browser, The Profiles Can Collide So You Can't Run Both At Once, And Your Stable Browser Might See Profile Versions From The Future (Google Chrome And Chromium Use Different Profile Directories By Default So Won't Collide). Use The Command-line Option: --user-data-dir=C:\tmp\my_debug_profile (replace The Path As Necessary) Using The IDE, Go To The Debugging Tab Of The Properties Of The Chrome Project, And Set The Command Arguments. Chrome Debug Log Enable Chrome Debug Logging To A File By Passing --enable-logging --v=1 Command-line Flags At Startup. Debug Builds Place The Chrome_debug.log File In The Out\Debug Directory. Release Builds Place The File In The Top Level Of The User Data Chromium App Directory, Which Is OS-version-dependent. For More Information, See Logging And User Data Directory Details. Symbol Server If You Are Debugging Official Google Chrome Release Builds, Use The Symbol Server: Https://chromium-browser-symsrv.commondatastorage.googleapis.com In Visual Studio, This Goes In Tools > Options Under Debugging > Symbols. You Should Set Up A Local Cache In A Empty Directory On Your Computer. In Windbg You Can Add This To Your Symbol Server Search Path With The Command Below, Where C:\symbols Is A Local Cache Directory: .sympath+ SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Alternately, You Can Set The _NT_SYMBOL_PATH Environment Variable To Include Both The Microsoft And Google Symbol Servers - VS, Windbg, And Other Tools Should Both Respect This Environment Variable: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Note That Symbol Servers Will Let The Debuggers Download Both The PE Files (DLLs And EXEs) And The PDB Files. Chrome Often Loads Third Party Libraries And Partial Symbols For Some Of These Are Also Public. For Example: AMD: Https://download.amd.com/dir/bin Nvidia: Https://driver-symbols.nvidia.com/ Intel: Https://software.intel.com/sites/downloads/symbols/ For Example, For Completeness, The Following Symbol Server Environment Variable Will Resolve All Of The Above Sources - But This Is More Than Is Normally Needed: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com;SRV\*C:\symbols\*https://download.amd.com/dir/bin;SRV\*C:\symbols\*https://driver-symbols.nvidia.com/;SRV\*C:\symbols\*https://software.intel.com/sites/downloads/symbols/ Source Indexing You Should Set Up Source Indexing In Your Debugger (.srcfix In Windbg, Tools-> Options-> Debugging-> General-> Enable Source Server Support In Visual Studio) So That The Correct Source Files Will Automatically Be Downloaded Based On Information In The Downloaded Symbols. Additionally, You Must Have Python In Your Path In Order For The Command That Fetches Source Files To Succeed; Launching The Debugger From The Same Environment As Where You Build Chromium Is An Easy Way To Ensure It's Present. This Is Highly Recommended When Debugging Released Google Chrome Builds Or Looking At Crash Dumps. Having The Correct Version Of The Source Files Automatically Show Up Saves Significant Time So You Should Definitely Set This. Multi-process Issues Chromium Can Be Challenging To Debug Because Of Its Multi-process Architecture. When You Select Run In The Debugger, Only The Main Browser Process Will Be Debugged. The Code That Actually Renders Web Pages (the Renderer) And The Plugins Will Be In Separate Processes That's Not (yet!) Being Debugged. The ProcessExplorer Tool Has A Process Tree View Where You Can See How These Processes Are Related. You Can Also Get The Process IDs Associated With Each Tab From The Chrome Task Manager (right-click On An Empty Area Of The Window Title Bar To Open). Automatically Attach To Child Processes There Are Two Visual Studio Extensions That Enable The Debugger To Automatically Attach To All Chrome Processes, So You Can Debug All Of Chrome At Once. Microsoft's Child Process Debugging Power Tool Is A Standalone Extension For This, And VsChromium Is Another Option That Bundles Many Other Additional Features. In Addition To Installing One Of These Extensions, You Must Run Visual Studio As Administrator, Or It Will Silently Fail To Attach To Some Of Chrome's Child Processes. Single-process Mode One Way To Debug Issues Is To Run Chromium In Single-process Mode. This Will Allow You To See The Entire State Of The Program Without Extra Work (although It Will Still Have Many Threads). To Use Single-process Mode, Add The Command-line Flag --single-process This Approach Isn't Perfect Because Some Problems Won't Manifest Themselves In This Mode And Some Features Don't Work And Worker Threads Are Still Spawned Into New Processes. Manually Attaching To A Child Process You Can Attach To The Running Child Processes With The Debugger. Select Tools > Attach To Process And Click The Chrome.exe Process You Want To Attach To. Before Attaching, Make Sure You Have Selected Only Native Code When Attaching To The Process This Is Done By Clicking Select... In The Attach To Process Window And Only Checking Native. If You Forget This, It May Attempt To Attach In "WebKit" Mode To Debug JavaScript, And You'll Get An Error Message "An Operation Is Not Legal In The Current State." You Can Now Debug The Two Processes As If They Were One. When You Are Debugging Multiple Processes, Open The Debug > Windows > Processes Window To Switch Between Them. Sometimes You Are Debugging Something That Only Happens On Startup, And Want To See The Child Process As Soon As It Starts. Use: --renderer-startup-dialog --no-sandbox You Have To Disable The Sandbox Or The Dialog Box Will Be Prohibited From Showing. When The Dialog Appears, Visit Tools > Attach To Process And Attach To The Process Showing The Renderer Startup Dialog. Now You're Debugging In The Renderer And Can Continue Execution By Pressing OK In The Dialog. Startup Dialogs Also Exist For Other Child Process Types: --gpu-startup-dialog, --ppapi-startup-dialog, --utility-startup-dialog, --plugin-startup-dialog (for NPAPI). For Utilities, You Can Add A Service Type --utility-startup-dialog=data_decoder.mojom.DataDecoderService. You Can Also Try The Vs-chromium Plug-in To Attach To The Right Processes. Semi-automatically Attaching The Debugger To Child Processes The Following Flags Cause Child Processes To Wait For 60 Seconds In A Busy Loop For A Debugger To Attach To The Process. Once Either Condition Is True, It Continues On; No Exception Is Thrown. --wait-for-debugger-children[=filter] The Filter, If Provided, Will Fire Only If It Matches The --type Parameter To The Process. Values Include Renderer, Plugin (for NPAPI), Ppapi, Gpu-process, And Utility. When Using This Option, It May Be Helpful To Limit The Number Of Renderer Processes Spawned, Using: --renderer-process-limit=1 Image File Execution Options Using Image File Execution Options (IFEO) Will Not Work Because CreateProcess() Returns The Handle To The Debugger Process Instead Of The Intended Child Process. There Are Also Issues With The Sandbox. Time Travel Debugging You Can Do Time Travel Debugging Using WinDbg Preview (must Be Installed From The Microsoft Store). This Lets You Execute A Program Forward And Backwards. After Capturing A Trace, You Can Set Breakpoints And Step Through Code As Normal, But Also Provides 'backwards' Commands (g-, T-, P-) So That You Can Go Back And Forth Through The Execution. It Is Especially Useful To Set Data Breakpoints (ba Command) And Reverse Continuing, So You Can See When A Certain Variable Was Last Changed To Its Current Value. Chromium Specifics: The Type Of Injection The Time Travel Tracer Needs To Perform Is Incompatible With The Chromium Sandbox. In Order To Record A Trace, You'll Need To Run With --no-sandbox. Chromium Cannot Run Elevated With Administrator Privileges, So The "Launch Executable (advance)" Option Won't Work, You'll Need To Attach After The Process Has Already Launched Via The Checkbox In The Bottom Right. If You Need To Record Startup-like Things, You'll Have To Use --{browser,gpu,renderer,utility}-startup-dialog, Then Attach (and Hope The Relevant Code Hasn't Executed Before That Point). JsDbg -- Data Structure Visualization You Can Install JsDbg As A Plugin For WinDbg Or Visual Studio. It Interactively Lets You Look At Data Structures (such As The DOM Tree, Accessibility Tree, Layout Object Tree, And Others) In A Web Browser As You Debug. See The JsDbg Site For Some Screen Shots And Usage Examples. This Also Works When Examining Memory Dumps (though Not Minidumps), And Also Works Together With Time Travel Debugging. Visual Studio Hints Debug Visualizers Chrome's Custom Debug Visualizers Should Be Added To The Pdb Files And Automatically Picked Up By Visual Studio. The Definitions Are In //tools/win/DebugVisualizers If You Need To Modify Them (the BUILD.gn File There Has Additional Instructions). Don't Step Into Trivial Functions The Debugger Can Be Configured To Automatically Not Step Into Functions Based On Regular Expression. Edit Default.natstepfilter In The Following Directory: For Visual Studio 2015: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2015\Visualizers (for The Current User Only) For Visual Studio 2017 Pro: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2017\Visualizers (for The Current User Only) Add Regular Expressions Of Functions To Not Step Into. Remember To Regex-escape And XML-escape Them, E.g. < For < And \. For A Literal Dot. Example: Operator New NoStepInto Operator Delete NoStepInto Std::.* NoStepInto WTF::.*Ptr ::.* NoStepInto This File Is Read At Start Of A Debugging Session (F5), So You Don't Need To Restart Visual Studio After Changing It. More Info: Microsoft Email Thread V8 And Chromium V8 Supports Many Command-line Flags That Are Useful For Debugging. V8 Command-line Flags Can Be Set Via The Chromium Command-line Flag --js-flags; For Instance: Chrome.exe --js-flags="--trace_exception --heap_stats" Note That Some V8 Command-line Flags Exist Only In The Debug Build Of V8. For A List Of All V8 Flags Try: Chrome.exe --js-flags="--help" Graphics Debugging GPU Acceleration Of Rendering Can Be More Easily Debugged With Tools. See: Graphics Debugging In Visual Studio 2013 Graphical Debugging With NVIDIA NSight Debugging On Another Machine Sometimes It's Useful To Debug Installation And Execution On A Machine Other Than Your Primary Build Box. To Run The Installer On Said Other Machine, First Build The Mini_installer Target On Your Main Build Machine (e.g., Autoninja -C Out\Debug Mini_installer). Next, On The Debug Machine: Make The Build Machine's Build Volume Available On The Debug Machine Either By Mounting It Locally (e.g., Z:\) Or By Crafting A UNC Path To It (e.g., \\builder\src) Open Up A Command Prompt And Change To A Local Disk Run Src\tools\win\copy-installer.bat In The Remote Checkout By Way Of The Mount (e.g., Z:\PATHTOCHECKOUT\src\...) Or UNC Path (e.g., \\builder\src\...). This Will Copy The Installer, DLLs, And PDBs Into Your Debug Machine's C:\out Or C:\build (depending On If You're Rocking The Component=shared_library Build Or Not) Run C:\out\Debug\mini_installer.exe With The Flags Of Your Choice To Install Chrome. This Can Take Some Time, Especially On A Slow Machine. Watch The Task Manager And Wait Until Mini_installer.exe Exits Before Trying To Launch Chrome (by Way Of The Shortcut(s) Created By The Installer) For Extra Pleasure, Add C:\out\Debug To Your _NT_SYMBOL_PATH Environment Variable Consider Reading The Documentation At The Top Of Copy-installer.bat To See How You Can Run It. It Tries To Be Smart And Copy The Right Things, But You May Need To Be Explicit (e.g., "copy-installer.bat Out Debug"). It Is Safe To Re-run The Script To Copy Only Modified Files (after A Rebuild, For Example). You Can Also Use The Zip Action Of The Isolate Scripts (tools\mb\mb.py) To Package All The Files For A Target Into A Single Zip File, For Example: Python Tools\mb\mb.py Zip Out/Release Base_unittests Base_unittests.zip Finding All Memory Allocations It Is Possible To Use Heap Snapshots To Get Call Stacks On All Outstanding Allocations That Use The OS Heap. This Works Particularly Well If Heap Snapshots Are Started As Soon As The Chrome Browser Process Is Created, But Before It Starts Running. Details Can Be Found In This Batch File. However, With PartitionAlloc Everywhere Most Chromium Allocations No Longer Use The Windows Heap So This Will Only Find A Subset Of Allocations, Mostly From OS DLLs. Find Memory Leaks Note: As With Heap Snapshots The Utility Of UMDH Is Greatly Reduced Now Because PartitionAlloc Everywhere Has Mostly Replaced The Windows Heap. The Windows Heap Manager Has A Really Useful Debug Flag, Where It Can Be Asked To Capture And Store A Stack Trace With Every Allocation. The Tool To Scrape These Stack Traces Out Of Processes Is UMDH, Which Comes With WinDbg. UMDH Is Great. It Will Capture A Snapshot Of The Heap State As Many Times As You Like, And It'll Do It Fairly Quickly. You Then Run It Again Against Either A Single Snapshot, Or A Pair Of Snapshots, At Which Time It'll Symbolize The Stack Traces And Aggregate Usage Up To Unique Stack Traces. Turning On The User Stack Trace Database For Chrome.exe With Gflags.exe Makes It Run Unbearably Slowly; However, Turning On The User Stack Trace Database On For The Browser Alone Is Just Fine. While It's Possible To Turn On The User Stack Database With The "!gflag" Debugging Extension, It's Too Late To Do This By The Time The Initial Debugger Breakpoint Hits. The Only Reasonable Way To Do This Is To Launch GFlags.exe, Enable The User Stack Trace Database (per Image Below), Launch Chrome Under The Debugger. Set A Breakpont When Chrome.dll Loads With "sxe Ld Chrome.dll". Step Up, To Allow Chrome.dll To Initialize. Disable The Stack Trace Database In GFlags.exe. Continue Chrome, Optionally Detaching The Debugger. Image GFlags.exe Settings For User Mode Stack Trace Database. If You Then Ever Suffer A Browser Memory Leak, You Can Snarf A Dump Of The Process With Umdh -p: > Chrome-browser-leak-umdh-dump.txt Which Can Then Typically Be "trivially" Analyzed To Find The Culprit. Miscellaneous Note That By Default Application Verifier Only Works With Non-official Builds Of Chromium. To Use Application Verifier On Official Builds You Need To Add --disable-features=RendererCodeIntegrity To Avoid Sandbox Crashes In Renderer Processes. See Crbug.com/1004989 For Details. See Also This Page. Application Verifier Is A Free Tool From Microsoft (available As Part Of The Windows SDK) That Can Be Used To Flush Out Programming Errors. Starting With M68 Application Verifier Can Be Enabled For Chrome.exe Without Needing To Disable The Sandbox. After Adding Chrome.exe To The List Of Applications To Be Stressed You Need To Expand The List Of Basics Checks And Disable The Leak Checks. You May Also Need To Disable Handles And Locks Checks Depending On Your Graphics Driver And Specific Chrome Version, But The Eventual Goal Is To Have Chrome Run With Handles And Locks Checks Enabled. When Bugs Are Found Chrome Will Trigger A Breakpoint So Running All Chrome Processes Under A Debugger Is Recommended. Chrome Will Run Much More Slowly Because Application Verifier Puts Every Heap Allocation On A Separate Page. Note That With PartitionAlloc Everywhere Most Chromium Allocations Don't Actually Go Through The Windows Heap And Are Therefore Unaffected By Application Verifier. You Can Check The Undocumented 'Cuzz' Checkbox In Application Verifier To Get The Windows Thread Scheduler To Add Some Extra Randomness In Order To Help Expose Race Conditions In Your Code. To Put A Breakpoint On CreateFile(), Add This Break Point: {,,kernel32.dll}_CreateFileW@28 {,,kernel32.dll} Specifies The DLL (context Operator). _ Prefix Means Extern "C". @28 Postfix Means _stdcall With The Stack Pop At The End Of The Function. I.e. The Number Of Arguments In BYTES. You Can Use DebugView From SysInternals Or Sawbuck To View LOG() Messages That Normally Go To Stderr On POSIX.” Subjects and Themes:

• Subjects: ➤  Debug - Build - Run - Compile - Chromium - Google - Chrome - Microsoft - Windows

Edition Identifiers:

• Internet Archive ID: debugging-chromium-on-windows

“When We Say We're Home : A Quartet Of Place And Memory” Metadata:

• Title: ➤  When We Say We're Home : A Quartet Of Place And Memory
• Language: English

“When We Say We're Home : A Quartet Of Place And Memory” Subjects and Themes:

• Subjects: Home - Families - Dwellings - Geographical perception

Edition Identifiers:

• Internet Archive ID: whenwesaywerehom0000unse

“Auto/biography And Pedagogy : Body, Memory, And Place In Teaching” Metadata:

• Title: ➤  Auto/biography And Pedagogy : Body, Memory, And Place In Teaching
• Author: Elbaz, Freema, author
• Language: English

“Auto/biography And Pedagogy : Body, Memory, And Place In Teaching” Subjects and Themes:

• Subjects: ➤  Education -- Biographical methods - Discourse analysis, Narrative - Critical pedagogy - Éducation -- Histoires de vie - Discours narratif - Pédagogie critique - EDUCATION -- Essays - EDUCATION -- Organizations & Institutions - EDUCATION -- Reference

Edition Identifiers:

• Internet Archive ID: autobiographyped0000elba

“Divisions Of The Heart : Elizabeth Bishop And The Art Of Memory And Place” Metadata:

• Title: ➤  Divisions Of The Heart : Elizabeth Bishop And The Art Of Memory And Place
• Language: English

“Divisions Of The Heart : Elizabeth Bishop And The Art Of Memory And Place” Subjects and Themes:

• Subjects: ➤  Bishop, Elizabeth, 1911-1979 -- Criticism and interpretation - Women and literature -- United States -- History -- 20th century - Autobiographical memory in literature - Place (Philosophy) in literature - Memory in literature - Setting (Literature) - Autobiographical memory in photographs

Edition Identifiers:

• Internet Archive ID: divisionsofheart0000unse

“Crowds In Rishon Lezion And Jerusalem Gathered To Accompany The Family Of Murdered Hostage, Shlomo Mantzur, On His Final Journey. Mantzur, 85, From Kibbutz Kissufim, Was The Oldest Hostage Held In Hamas Captivity. His Body Was Returned To Israel, And His Funeral Took Take Place This Sunday. May His Memory Be A Blessing 🕯️ 🎥 @thejerusalempost” Metadata:

• Title: ➤  Crowds In Rishon Lezion And Jerusalem Gathered To Accompany The Family Of Murdered Hostage, Shlomo Mantzur, On His Final Journey. Mantzur, 85, From Kibbutz Kissufim, Was The Oldest Hostage Held In Hamas Captivity. His Body Was Returned To Israel, And His Funeral Took Take Place This Sunday. May His Memory Be A Blessing 🕯️ 🎥 @thejerusalempost
• Author: israelinusa

“Crowds In Rishon Lezion And Jerusalem Gathered To Accompany The Family Of Murdered Hostage, Shlomo Mantzur, On His Final Journey. Mantzur, 85, From Kibbutz Kissufim, Was The Oldest Hostage Held In Hamas Captivity. His Body Was Returned To Israel, And His Funeral Took Take Place This Sunday. May His Memory Be A Blessing 🕯️ 🎥 @thejerusalempost” Subjects and Themes:

• Subjects: TikTok - video

Edition Identifiers:

• Internet Archive ID: TikTok-7477976728992845087

“Memory And Liturgy : The Place Of Memory In The Composition And Practice Of Liturgy” Metadata:

• Title: ➤  Memory And Liturgy : The Place Of Memory In The Composition And Practice Of Liturgy
• Author: Atkins, Peter, 1936-
• Language: English

“Memory And Liturgy : The Place Of Memory In The Composition And Practice Of Liturgy” Subjects and Themes:

• Subjects: Liturgics - Liturgie - Gedachtenis

Edition Identifiers:

• Internet Archive ID: memoryliturgypla0000atki

“Charles E. Heaney : Memory, Imagination, And Place” Metadata:

• Title: ➤  Charles E. Heaney : Memory, Imagination, And Place
• Author: Hull, Roger
• Language: English

“Charles E. Heaney : Memory, Imagination, And Place” Subjects and Themes:

• Subjects: ➤  Heaney, Charles, 1897-1981 -- Exhibitions - Artists -- Oregon -- Biography

Edition Identifiers:

• Internet Archive ID: charleseheaneyme0000hull

“Place, Memory, And Healing : An Archaeology Of Anatolian Rock Monuments” Metadata:

• Title: ➤  Place, Memory, And Healing : An Archaeology Of Anatolian Rock Monuments
• Author: Harmanşah, Öm©ơr
• Language: English

“Place, Memory, And Healing : An Archaeology Of Anatolian Rock Monuments” Subjects and Themes:

• Subjects: ➤  Landscape archaeology -- Turkey - Monuments -- Turkey - Collective memory -- Turkey - Antiquities - Collective memory - Landscape archaeology - Monuments - Landskapsarkeologi - Fornlämningar - Monument - Kollektivt minne - Turkey -- Antiquities - Turkey

Edition Identifiers:

• Internet Archive ID: placememoryheali0000harm

“The Age Of Wild Ghosts : Memory, Violence, And Place In Southwest China” Metadata:

• Title: ➤  The Age Of Wild Ghosts : Memory, Violence, And Place In Southwest China
• Author: Mueggler, Erik, 1962-
• Language: English

“The Age Of Wild Ghosts : Memory, Violence, And Place In Southwest China” Subjects and Themes:

• Subjects: ➤  Ethnology -- China -- Yunnan Sheng - Yunnan Sheng (China) -- Social conditions

Edition Identifiers:

• Internet Archive ID: ageofwildghostsm0000mueg

“Memory, Place, Desire : Contemporary Art Of The Maghreb And Maghreb Diaspora” Metadata:

• Title: ➤  Memory, Place, Desire : Contemporary Art Of The Maghreb And Maghreb Diaspora
• Author: Solomon, Carol
• Language: English

“Memory, Place, Desire : Contemporary Art Of The Maghreb And Maghreb Diaspora” Subjects and Themes:

• Subjects: ➤  Solomon, Carol - Art, North African -- 21st century -- Exhibitions - Art, Algerian -- 21st century -- Exhibitions - Art, Tunisian -- 21st century -- Exhibitions - Art, Moroccan -- 21st century -- Exhibitions - Art, Arab -- 21st century -- Exhibitions - Art, Algerian - Art, Arab - Art, Moroccan - Art, North African - Art, Tunisian

Edition Identifiers:

• Internet Archive ID: memoryplacedesir0000solo

“In Memory Of The Brave Men Who Met Their Death While In The Discharge Of Their Duty At The St. Urbain Street Fire On Sunday, April 29, 1877 [microform] : And Whose Funerals Are To Take Place This Day” Metadata:

• Title: ➤  In Memory Of The Brave Men Who Met Their Death While In The Discharge Of Their Duty At The St. Urbain Street Fire On Sunday, April 29, 1877 [microform] : And Whose Funerals Are To Take Place This Day
• Author: Crankshaw, James, 1844-1921
• Language: English

“In Memory Of The Brave Men Who Met Their Death While In The Discharge Of Their Duty At The St. Urbain Street Fire On Sunday, April 29, 1877 [microform] : And Whose Funerals Are To Take Place This Day” Subjects and Themes:

• Subjects: ➤  Fires -- Quebec (Province) Montréal - Incendies -- Québec (Province) Montréal

Edition Identifiers:

• Internet Archive ID: cihm_00374

“Cooper & Gorfer And Doug Cooper: Divergent Paths, Shared Themes Of Identity, Memory, And Place In Contemporary Art” Metadata:

• Title: ➤  Cooper & Gorfer And Doug Cooper: Divergent Paths, Shared Themes Of Identity, Memory, And Place In Contemporary Art
• Author: Jeffrey A Brick
• Language: English

“Cooper & Gorfer And Doug Cooper: Divergent Paths, Shared Themes Of Identity, Memory, And Place In Contemporary Art” Subjects and Themes:

• Subjects: ➤  Cooper & Gorfer - Sarah Cooper - Nina Gorfer - photography - collage - mixed media - identity - displacement - migration - utopia - Sweden - Stockholm - Gothenburg - Berlin - Afghanistan - Syria - Iran - Somalia - Kyrgyzstan - Qatar - "Between These Folded Walls - Utopia" - "I Know Not These My Hands" - "Under Nomadic Surfaces" - "Sirens" - Hasselblad - portraiture - women - exhibitions - art - contemporary art - memory - travel - refugees - cultural symbols - political themes - social themes - empowerment - artistic techniques - Doug Cooper - muralist - artist - architect - Pittsburgh - Forbes Field - architectural places - urban landscapes - Heinz History Center - Philadelphia - Carnegie Mellon University - Seattle - Rome - art education - drawing - "Steel Shadows" - "Drawing and Perceiving" - Nazi-looted art - MFAA - Cubism - history - community collaboration - senior citizens - books - exhibitions.

Edition Identifiers:

• Internet Archive ID: ➤  cooper-gorfer-between-folded-walls-utopia

“Circadian Clocks And Memory: Time-place Learning.” Metadata:

• Title: ➤  Circadian Clocks And Memory: Time-place Learning.
• Authors: Mulder, C. K.Gerkema, M. P.Van der Zee, E. A.
• Language: English

Edition Identifiers:

• Internet Archive ID: pubmed-PMC3622895

“California Vieja : Culture And Memory In A Modern American Place” Metadata:

• Title: ➤  California Vieja : Culture And Memory In A Modern American Place
• Author: ➤  Young, Phoebe S. K. (Phoebe Schroeder Kropp), 1970-
• Language: English

“California Vieja : Culture And Memory In A Modern American Place” Subjects and Themes:

• Subjects: ➤  Architecture, Domestic -- California, Southern - Architecture, Spanish colonial -- California, Southern - Architecture -- California, Southern -- History -- 20th century - Landscapes -- California, Southern - Mexican Americans -- California -- Social conditions - Memory -- Social aspects -- California - El Camino Real (Calif.)

Edition Identifiers:

• Internet Archive ID: californiaviejac0000youn

“Place And Memory In The Singing Crane Garden” Metadata:

• Title: ➤  Place And Memory In The Singing Crane Garden
• Author: Schwarcz, Vera, 1947-
• Language: English

Edition Identifiers:

• Internet Archive ID: placememoryinsin0000schw

“Christine M. DeLucia, "Memory Lands: King Philip's War And The Place Of Violence In The Northeast" (Yale UP, 2018)” Metadata:

• Title: ➤  Christine M. DeLucia, "Memory Lands: King Philip's War And The Place Of Violence In The Northeast" (Yale UP, 2018)
• Author: ➤  New Books in Native American Studies

Edition Identifiers:

• Internet Archive ID: ➤  j9nmpbyi2h7ylxlkxkbjllheecn4b0ehlb6nol2y

“The Place Of Mental Imagery And Memory Among Mental Functions” Metadata:

• Title: ➤  The Place Of Mental Imagery And Memory Among Mental Functions
• Author: Kuhlmann, Fred
• Language: English

Edition Identifiers:

• Internet Archive ID: jstor-1412383

“The Home Place : A Memory And Celebration” Metadata:

• Title: ➤  The Home Place : A Memory And Celebration
• Author: Drake, Robert, 1930-
• Language: English

“The Home Place : A Memory And Celebration” Subjects and Themes:

• Subjects: Drake, Robert, 1930- - Drake family - Families -- Tennessee, West - Tennessee, West -- Biography

Edition Identifiers:

• Internet Archive ID: homeplacememoryc0000drak

“20140227 Music Memory Place 1 Race Recollections From Near And Far” Metadata:

• Title: ➤  20140227 Music Memory Place 1 Race Recollections From Near And Far
• Author: MelbourneFreeUniversity
• Language: English

“20140227 Music Memory Place 1 Race Recollections From Near And Far” Subjects and Themes:

• Subjects: race - history

Edition Identifiers:

• Internet Archive ID: ➤  20140227MusicMemoryPlace1RaceRecollectionsFromNearAndFar

“Place And Displacement In Jewish History And Memory : Zakor V'makor” Metadata:

• Title: ➤  Place And Displacement In Jewish History And Memory : Zakor V'makor
• Language: English

“Place And Displacement In Jewish History And Memory : Zakor V'makor” Subjects and Themes:

• Subjects: Jews -- Identity -- Congresses - Jewish diaspora -- Congresses

Edition Identifiers:

• Internet Archive ID: placedisplacemen0000unse

“Placing Memory And Remembering Place In Canada” Metadata:

• Title: ➤  Placing Memory And Remembering Place In Canada
• Language: English

“Placing Memory And Remembering Place In Canada” Subjects and Themes:

• Subjects: ➤  Human geography -- Canada - Collective memory -- Canada - Geography -- Social aspects -- Canada - Civilization - Collective memory - Geography -- Social aspects - Human geography - Mémoire collective -- Canada - Géographie humaine -- Canada - Géographie -- Aspect social -- Canada - Canada -- Civilization - Canada - Canada -- Civilisation - Memoire collective -- Canada - Geographie humaine -- Canada - Geographie -- Aspect social -- Canada

Edition Identifiers:

• Internet Archive ID: placingmemoryrem0000unse

“Wilderness And The Heart : Henry Bugbee's Philosophy Of Place, Presence, And Memory” Metadata:

• Title: ➤  Wilderness And The Heart : Henry Bugbee's Philosophy Of Place, Presence, And Memory
• Language: English

“Wilderness And The Heart : Henry Bugbee's Philosophy Of Place, Presence, And Memory” Subjects and Themes:

• Subjects: ➤  Bugbee, Henry Greenwood, Jr. Inward morning - Philosophy

Edition Identifiers:

• Internet Archive ID: wildernesshearth0000unse

“ERIC ED273264: Applications Of Microcomputer Search-Type Adventure Games In Research On Spatial Orientation, Place Location, And Memory For Places.” Metadata:

• Title: ➤  ERIC ED273264: Applications Of Microcomputer Search-Type Adventure Games In Research On Spatial Orientation, Place Location, And Memory For Places.
• Author: ERIC
• Language: English

“ERIC ED273264: Applications Of Microcomputer Search-Type Adventure Games In Research On Spatial Orientation, Place Location, And Memory For Places.” Subjects and Themes:

• Subjects: ➤  ERIC Archive - Comparative Analysis - Computer Graphics - Computer Simulation - Grade 4 - Grade 5 - Instructional Effectiveness - Intermediate Grades - Intermode Differences - Recall (Psychology) - Sex Differences - Spatial Ability - Student Attitudes

Edition Identifiers:

• Internet Archive ID: ERIC_ED273264

“Maps And Memory In Early Modern England : A Sense Of Place” Metadata:

• Title: ➤  Maps And Memory In Early Modern England : A Sense Of Place
• Author: Sanford, Rhonda Lemke
• Language: English

“Maps And Memory In Early Modern England : A Sense Of Place” Subjects and Themes:

• Subjects: ➤  English literature -- Early modern, 1500-1700 -- History and criticism - Place (Philosophy) in literature - Cartography -- England -- History -- 16th century - Cartography -- England -- History -- 17th century - Geography in literature - Memory in literature - Maps in literature - England -- Maps -- History

Edition Identifiers:

• Internet Archive ID: mapsmemoryinearl0000sanf

“Eye On Palestine - The Stone Was Never Just A Target; It Was The Beginning Of Catastrophes Aimed At Uprooting Our Roots, Erasing Every Laugh And Every Memory Woven Through Generations, As They Attempt To Rewrite History Without Leaving Us A Place Or A Voice.” Metadata:

• Title: ➤  Eye On Palestine - The Stone Was Never Just A Target; It Was The Beginning Of Catastrophes Aimed At Uprooting Our Roots, Erasing Every Laugh And Every Memory Woven Through Generations, As They Attempt To Rewrite History Without Leaving Us A Place Or A Voice.
• Author: Eye on Palestine

“Eye On Palestine - The Stone Was Never Just A Target; It Was The Beginning Of Catastrophes Aimed At Uprooting Our Roots, Erasing Every Laugh And Every Memory Woven Through Generations, As They Attempt To Rewrite History Without Leaving Us A Place Or A Voice.” Subjects and Themes:

• Subjects: Twitter - video

Edition Identifiers:

• Internet Archive ID: twitter-1825617481425142130

“Memory In Place - Locating Colonial Histories And Commemoration” Metadata:

• Title: ➤  Memory In Place - Locating Colonial Histories And Commemoration
• Language: English

“Memory In Place - Locating Colonial Histories And Commemoration” Subjects and Themes:

• Subjects: colonial history - colonialism - Indigenous Australia - commemoration - book

Edition Identifiers:

• Internet Archive ID: oapen-20.500.12657-87975

“A Place To Call Home : Tradition, Style, And Memory In The New American House” Metadata:

• Title: ➤  A Place To Call Home : Tradition, Style, And Memory In The New American House
• Author: Schafer, Gil, III
• Language: English

“A Place To Call Home : Tradition, Style, And Memory In The New American House” Subjects and Themes:

• Subjects: ➤  Interior decoration -- United States -- 21st century -- Pictorial works - Architecture, Domestic -- United States

Edition Identifiers:

• Internet Archive ID: placetocallhomet0000scha

“Champlin Cemetery - A Place Of Memory And Love” Metadata:

• Title: ➤  Champlin Cemetery - A Place Of Memory And Love
• Author: QCTV
• Language: English

“Champlin Cemetery - A Place Of Memory And Love” Subjects and Themes:

• Subjects: ➤  Minnesota - Andover - Quad Cities Community Television - QCTV - Public Access TV - Community Media - PEG - Youtube - MN - Anoka - Champlin - Ramsey - 2021

Edition Identifiers:

• Internet Archive ID: ➤  qctvmn-Champlin_Cemetery_-_A_Place_of_Memory_and_Love

“Spaces For The Sacred: Place, Memory And Identity” Metadata:

• Title: ➤  Spaces For The Sacred: Place, Memory And Identity
• Author: Philip Sheldrake
• Language: English

Edition Identifiers:

• Internet Archive ID: spacesforsacredp0000phil

“Searching For Place : Ukrainian Displaced Persons, Canada, And The Migration Of Memory” Metadata:

• Title: ➤  Searching For Place : Ukrainian Displaced Persons, Canada, And The Migration Of Memory
• Author: Luciuk, Lubomyr Y., 1953-
• Language: English

“Searching For Place : Ukrainian Displaced Persons, Canada, And The Migration Of Memory” Subjects and Themes:

• Subjects: ➤  Refugees -- Government policy -- Canada - Refugees -- Ukraine - Ukrainians -- Canada -- History - Ukrainian Canadians -- Attitudes - Ukrainian Canadians -- History

Edition Identifiers:

• Internet Archive ID: searchingforplac0000luci

“Geography And Memory : Explorations In Identity, Place And Becoming” Metadata:

• Title: ➤  Geography And Memory : Explorations In Identity, Place And Becoming
• Language: English

“Geography And Memory : Explorations In Identity, Place And Becoming” Subjects and Themes:

• Subjects: ➤  Cultural geography -- Congresses - Human geography -- Congresses - Collective memory -- Philosophy -- Congresses

Edition Identifiers:

• Internet Archive ID: geographymemorye0000unse

“Stand The Sacred Tree : Journeys In Place And Memory” Metadata:

• Title: ➤  Stand The Sacred Tree : Journeys In Place And Memory
• Author: Weier, John, 1949-
• Language: English

“Stand The Sacred Tree : Journeys In Place And Memory” Subjects and Themes:

• Subjects: Weier, John, 1949- -- Travel - Voyages and travels

Edition Identifiers:

• Internet Archive ID: standsacredtreej0000weie

“Lewis & Clark Territory : Contemporary Artists Revisit Place, Race, And Memory” Metadata:

• Title: ➤  Lewis & Clark Territory : Contemporary Artists Revisit Place, Race, And Memory
• Author: Hushka, Rock, 1966-
• Language: English

“Lewis & Clark Territory : Contemporary Artists Revisit Place, Race, And Memory” Subjects and Themes:

• Subjects: ➤  Lewis and Clark Expedition (1804-1806) -- Influence -- Exhibitions - Lewis and Clark Expedition - Art, American -- 20th century -- Exhibitions - Art, American -- 21st century -- Exhibitions - Indian art -- United States -- Exhibitions - National characteristics, American, in art -- Exhibitions - Art, American - Indian art - Influence (Literary, artistic, etc.) - National characteristics, American, in art - West (U.S.) -- In art -- Exhibitions - United States - United States, West

Edition Identifiers:

• Internet Archive ID: lewisclarkterrit0000hush

“Japanese Capitals In Historical Perspective : Place, Power And Memory In Kyoto, Edo And Tokyo” Metadata:

• Title: ➤  Japanese Capitals In Historical Perspective : Place, Power And Memory In Kyoto, Edo And Tokyo
• Language: English

“Japanese Capitals In Historical Perspective : Place, Power And Memory In Kyoto, Edo And Tokyo” Subjects and Themes:

• Subjects: ➤  Cities and towns -- Japan -- History - Kyoto (Japan) - Tokyo (Japan)

Edition Identifiers:

• Internet Archive ID: japanesecapitals0000unse

“Perirhinal Cortical Inactivation Impairs Object-in-place Memory And Disrupts Task-dependent Firing In Hippocampal CA1, But Not In CA3.” Metadata:

• Title: ➤  Perirhinal Cortical Inactivation Impairs Object-in-place Memory And Disrupts Task-dependent Firing In Hippocampal CA1, But Not In CA3.
• Authors: Lee, InahPark, Seong-Beom
• Language: English

Edition Identifiers:

• Internet Archive ID: pubmed-PMC3743073

“Human Single-unit Recordings Reveal A Link Between Place-cells And Episodic Memory.” Metadata:

• Title: ➤  Human Single-unit Recordings Reveal A Link Between Place-cells And Episodic Memory.
• Authors: Niediek, JohannesBain, Jonathan
• Language: English

Edition Identifiers:

• Internet Archive ID: pubmed-PMC4148621

“Salem : Place, Myth, And Memory” Metadata:

• Title: ➤  Salem : Place, Myth, And Memory
• Language: English

“Salem : Place, Myth, And Memory” Subjects and Themes:

• Subjects: ➤  Group identity -- Massachusetts -- Salem - Human geography -- Massachusetts -- Salem - HISTORY -- United States -- State & Local -- General - HISTORY -- United States -- State & Local -- Middle Atlantic (DC, DE, MD, NJ, NY, PA) - HISTORY -- United States -- State & Local -- New England (CT, MA, ME, NH, RI, VT) - Group identity - Human geography - Social conditions - Salem (Mass.) -- History - Salem (Mass.) -- Social conditions - Massachusetts -- Salem

Edition Identifiers:

• Internet Archive ID: salemplacemythme0000unse

“In/different Spaces : Place And Memory In Visual Culture” Metadata:

• Title: ➤  In/different Spaces : Place And Memory In Visual Culture
• Author: Burgin, Victor
• Language: English

“In/different Spaces : Place And Memory In Visual Culture” Subjects and Themes:

• Subjects: ➤  Burgin, Victor, 1941- - Aesthetics - Place (Philosophy) - Memory (Philosophy) - Vision - Artes - Cultura - Espaço (filosofia) - Comunicação visual (aspectos sociais) - Beeldcultuur - Ruimte (algemeen) - Plaats - Culturele aspecten - Esthetica - Esthétique - Lieu (Philosophie) - Mémoire (Philosophie) - Mémoire (philosophie) - Image (philosophie) - Ästhetik

Edition Identifiers:

• Internet Archive ID: indifferentspace00burg

“ERIC ED262328: Domain Specific Knowledge And Memory Performance In The Work Place.” Metadata:

• Title: ➤  ERIC ED262328: Domain Specific Knowledge And Memory Performance In The Work Place.
• Author: ERIC
• Language: English

“ERIC ED262328: Domain Specific Knowledge And Memory Performance In The Work Place.” Subjects and Themes:

• Subjects: ➤  ERIC Archive - Adult Development - Age Differences - Aging (Individuals) - Classification - Job Performance - Memory - Older Adults - Performance - Recall (Psychology) - Work Experience

Edition Identifiers:

• Internet Archive ID: ERIC_ED262328

“Social Identities In The Classic Maya Northern Lowlands : Gender, Age, Memory, And Place” Metadata:

• Title: ➤  Social Identities In The Classic Maya Northern Lowlands : Gender, Age, Memory, And Place
• Author: Ardren, Traci, author
• Language: English

“Social Identities In The Classic Maya Northern Lowlands : Gender, Age, Memory, And Place” Subjects and Themes:

• Subjects: ➤  Mayas -- Yucatán Peninsula -- Social conditions - Maya -- Yucatán Peninsula -- Antiquities - Group identity -- Yucatán Peninsula -- History - Social structure -- Yucatán Peninsula -- History - Social archaeology -- Yucatán Peninsula - Yucatán Peninsula -- Antiquities

Edition Identifiers:

• Internet Archive ID: socialidentities0000ardr

“Imaginal Memory And The Place Of Hiroshima” Metadata:

• Title: ➤  Imaginal Memory And The Place Of Hiroshima
• Author: Perlman, Michael, 1957-
• Language: English

“Imaginal Memory And The Place Of Hiroshima” Subjects and Themes:

• Subjects: ➤  Memory - Imagery (Psychology) - Nuclear warfare -- Psychological aspects - Peace -- Psychological aspects - Archetype (Psychology) - Hiroshima-shi (Japan) -- History -- Bombardment, 1945

Edition Identifiers:

• Internet Archive ID: imaginalmemorypl0000perl

“The Home Place: A Memory And A Celebration” Metadata:

• Title: ➤  The Home Place: A Memory And A Celebration
• Author: Drake, Robert, 1930-
• Language: English

“The Home Place: A Memory And A Celebration” Subjects and Themes:

• Subjects: Drake Robert 1930- - Drake family - Families--Tennessee West - Tennessee West--Biography

Edition Identifiers:

• Internet Archive ID: drake-home-place

“California Vieja : Culture And Memory In A Modern American Place” Metadata:

• Title: ➤  California Vieja : Culture And Memory In A Modern American Place
• Author: ➤  Kropp, Phoebe S. (Phoebe Schroeder), 1970-
• Language: English

“California Vieja : Culture And Memory In A Modern American Place” Subjects and Themes:

• Subjects: ➤  Architecture, Domestic -- California, Southern - Architecture, Spanish colonial -- California, Southern - Architecture -- California, Southern -- 20th century - Landscapes -- California, Southern - Mexican Americans -- California -- Social conditions - Memory -- Social aspects -- California - El Camino Real (Calif.)

Edition Identifiers:

• Internet Archive ID: californiaviejac0000krop

“Place Of Discursive Memory And Scenography In The Lausanne Covenant” Metadata:

• Title: ➤  Place Of Discursive Memory And Scenography In The Lausanne Covenant
• Language: English

“Place Of Discursive Memory And Scenography In The Lausanne Covenant” Subjects and Themes:

• Subjects: Lausanne 74 - Marxism - Protestantism - Religious Discourse - Place of discursive Memory.

Edition Identifiers:

• Internet Archive ID: 15placeof

“Architecture: Space, Place, And Memory” Metadata:

• Title: ➤  Architecture: Space, Place, And Memory
• Author: Wagih Fawzi Youssef
• Language: English

“Architecture: Space, Place, And Memory” Subjects and Themes:

• Subjects: ➤  architecture - spatial images - collective memory - reasoning - assimilation - change - presentism

Edition Identifiers:

• Internet Archive ID: ➤  ArchitectureSpacePlaceAndMemory

“Blockage Of Glucocorticoid Receptors During Memory Acquisition, Retrieval And Reconsolidation Prevents The Expression Of Morphine-induced Conditioned Place Preferences In Mice” Metadata:

• Title: ➤  Blockage Of Glucocorticoid Receptors During Memory Acquisition, Retrieval And Reconsolidation Prevents The Expression Of Morphine-induced Conditioned Place Preferences In Mice
• Authors: ➤  Fan, Yao-DongNiu, Hai-ChenHuma, TanzeelLi, LingWang, Gui-MeiXu, Li-QiRen, HeMa, Yuan-YeYu, Hua-Lin

Edition Identifiers:

• Internet Archive ID: ➤  zoological-research-2095-8137-3302

Edition Identifiers:

• Internet Archive ID: the-lean-startup-erick-ries-1

“August 15, 2014 Week Eight: "Chautauqua Amphitheater: Place And Memory" - Chautauqua Institution Archives Heritage Lecture Series” Metadata:

• Title: ➤  August 15, 2014 Week Eight: "Chautauqua Amphitheater: Place And Memory" - Chautauqua Institution Archives Heritage Lecture Series
• Author: ➤  Center for the Study of Art, Architecture, History & Nature (C-SAAHN)

“August 15, 2014 Week Eight: "Chautauqua Amphitheater: Place And Memory" - Chautauqua Institution Archives Heritage Lecture Series” Subjects and Themes:

• Subjects: ➤  C-SAAHN - Chautauqua Stories, Chautauqua Arhives Heritage Lecture - Jon Schmitz - Avrom Posner

Edition Identifiers:

• Internet Archive ID: WS400675