Okay, this is take 2 because my first post was unceremoniously ‘disappeared’.

My BTS team is getting geared up for writing Unit Tests in JUnit. We’re using Eclipse with subclipse for SVN. Two teammates are Windows, one Linux and me on the Mac. Mac’s version of Java is Apple’s not Sun’s so my JRE profile is not compatible with theirs. This means I will be using my Linux VM for the project – getting to know Ubuntu a little better.

Today’s the first day of significant coding and I am already frustrated that I have to reach back to use the ctrl key instead of my trusty apple key for shortcuts. Also the tilde key actually produces < and there's no delete functionality (what Mac calls delete is really backspace). So I have found a solution and here it is: First, create a file (mine is called wickedCoolKeycodeFinder – you know, so I can always find it again)
and in that file put this:
xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode ([0-9]*).* (.*, (.*)).*$/1 2/p'

chmod +x this file and then run it to produce a neat little window that will tell you what keycode is returned for whatever key you press.

Then, once you know the keycodes of the keys you want to map, create a file called .xmodmaprc and in that file I put:

!this sorts out the apple key + backspace to do delete
keycode 113 = BackSpace Terminate_Server Delete
! map tilde and grave
keycode 49 = grave asciitilde
!map apple key to ctrl
remove Control = Control_L
keycode 115 = Control_L
keycode 116 = Control_L
add Control = Control_L


Now I just need to figure out how I can get my two-finger scrolling on the touchpad to work and I’ll be a Linux user forever!

So for my 0.3 release of sourceServer, I am tasked with altering the code in symbolstore.py so that it will track the source files and then call pdbstr.exe on them.

To do this, I need to understand what PDBSTR.EXE does. This is what I have to go on:

Once the code has looked at all the source files in the PDB file, it’s time to call PDBSTR.EXE to write the index stream, called SRCSRV, to the PDB file. When debugging, the debugger looks for this stream. If it is found, the debugger knows there’s a source server involved and calls into SRCSRV.DLL to execute the version control system to ensure the right file is accessed.

I’ve been studying the pdb files pre and post indexing to gain insight into what happens when I use the Debugging for Windows srcsrv tools. Circling the symbolstore.py code getting ready to make changes to see what I can do.

Any minute now the big picture will come into focus…back to my pdb files.

Just a quick post to share my SourceServer Presentation if anyone’s interested in an overview of what my project this term in DPS909 has entailed.