Just a quick note here—you can still debug a program using gdb if the debug information exists in the executable,
even if gdb doesn't have access to the source files.
It will still print out filenames and line numbers,
and you can still examine the contents of variables.
I just spent an hour with TS debugging an issue with “Project: Lumbergh” on our lab machines,
running gdb in one terminal,
and an editor in a second terminal following the files and line numbers given by gdb.
Not quite the optimum experience,
but at least it was doable.
I'm also not sure what it says about “Project: Lumbergh” that the issue turned out to be a configuration issue—the configuration was legal at one time,
but not with a newer version of the code.
I think the codebase is slowly turning into a big ball of mud.
You have my permission to link freely to any entry here. Go
ahead, I won't bite. I promise.
The dates are the permanent links to that day's entries (or
entry, if there is only one entry). The titles are the permanent
links to that entry only. The format for the links are
simple: Start with the base link for this site: https://boston.conman.org/, then add the date you are
interested in, say 2000/08/01,
so that would make the final URL:
https://boston.conman.org/2000/08/01
You can also specify the entire month by leaving off the day
portion. You can even select an arbitrary portion of time.
You may also note subtle shading of the links and that's
intentional: the “closer” the link is (relative to the
page) the “brighter” it appears. It's an experiment in
using color shading to denote the distance a link is from here. If
you don't notice it, don't worry; it's not all that
important.
It is assumed that every brand name, slogan, corporate name,
symbol, design element, et cetera mentioned in these pages is a
protected and/or trademarked entity, the sole property of its
owner(s), and acknowledgement of this status is implied.
