Fastgrep, a cache for grep

Sooner or later, you’ll find that you need to know where to find a certain piece of text that ctags does not index, and grep is just not fast enough. Say, you’re trying to match that log line you see every one in a while to the specific printf(“I’m here!\n”) that produced it.

Working on any reasonable sized project, searching for free-form text means you’ll need some kind of indexing; grep will work, but you’ll end up having to wait a couple of minutes between searches. Funny thing, we can probably speed up grep quite easily. Long story short, you can find a grep cache here: Fastgrep.

So, how does it work? If we reason a bit about how grep will spend time we can probably assume the following:

  1. Re-positioning the disk head to find the next file to grep
  2. Reading file contents
  3. Opening & closing files
  4. Actually grepping

I didn’t actually check how closely this “benchmark” resembles reality, but it seems reasonable to assume that most of the time grep spends searching for a string in a big project, is actually wasted in I/O, and more cores won’t help.

After a quick Google search I didn’t come up with any already available grep cache, so I rolled up a quick version myself which you can find here: Fastgrep. The idea behind it is very simple, if most of the time is wasted accessing files, then just cat every file in the project together and grep that one instead.

Since the grepcache is actually a merged copy of all the files in the project, it can quickly get out of sync with the rest of the code. To somewhat improve this the index file is only used to get the list of files where a string might be found; these files are then grepped for the real results. This only helps a little bit and eventually everything gets out of sync, but I found that rebuilding the cache in a post-merge git hook (or a post-commit svn hook) is more than enough to make fastgrep more than usable.

Fixing keyboard layouts in Ubuntu. Scarier than it seems.

At the moment of writing this post there is an open bug in Ubuntu, still active in 11.04, that makes your keyboard layout revert to whatever GDM wants. Apparently this is caused by GDM failing to synch with the preferences of the session, so if you change your layout (even if you delete the previous one) the change will be reverted next time you login. There seems to be no fix coming soon, so this magic incantation might work if you have this problem:

sudo dpkg-reconfigure keyboard-configuration

This will ask you a lot of questions about your keyboard, good luck guessing. It kind of reminds me the Windows 95 install process, in which erring the keyboard layout meant it was probably easier to just format and reinstall everything all over again. With some luck, next time you reboot your Ubuntu will actually remember your keyboard preference. If not, just take this as an opportunity to learn a foreign language.

Having keyboard problems? You may also be interested in learning how to activate tildes and accents for a USA keyboard layout in Ubuntu.

Getting a stacktrace on C/C++: Mapping function pointers to function names on runtime

Last time we talked about mapping function addresses to names (albeit mangled) in object files; we can also get this information during runtime:

Glibc to the aid

Let’s go one step back: how to get the current stacktrace. Turns out glibc already has a nice feature to get the current stacktrace. Going back to our original program, with some minor changes:

struct Caller { Caller *addr; };
void bt_by_hand() {
    // Get the stack base ptr from a register
    void *sp;
    asm("movl %%ebp,%0" : "=r"(sp));

    // Loop through every caller
    cout << "Hand made stack walker" << endl;
    Caller *caller = (Caller*)sp;
    while (caller) {
        cout << (((void**)caller)[1]) << endl;
        caller = caller->addr;

#include <execinfo.h>
void bt_glibc() {
    void* buffer[10];
    int frames = backtrace(buffer, sizeof buffer);

    cout << "glibc stack walker" << endl;
    for (int i=0; i < frames; ++i) cout << buffer[i] << endl;

void bar(int, float) {

Clearly using glibc’s version is much cleaner, but will they yield the same results? Turns out not:

Hand made stack walker
glibc stack walker

Similar, but not quite.

  • The first address in the glibc’s stack walker correspond to the bt_glibc, and more importantly since the real glibc backtrace is a function call itself it’s easy to get that function into the stack. We don’t even consider that case on our hand made stack walker. First difference explained.
  • The second address should correspond to bar, but one is 0x80487b0 and the other is 0x80487b5. Again, it makes sense: since the void* is actually the return address for EIP if we check the dissasembly we’ll find that the 5 bytes difference correspond to the next instruction to be executed.
  • 0x80487d5 is the return address for main, which is the same for both.
  • The rest of the stack is easy: we stop at main, glibc keeps walking the stack inside glibc itself. Not so important for us, anyway.

Name translations

We have a bunch of pointers. How can we get real function names now? Well, the easiest way is to use glibc’s backtrace_symbols_fd, like this:

    int frames = backtrace(buffer, sizeof buffer);
    backtrace_symbols_fd(buffer, frames, 1);

On my machine, when running “g++ -rdynamic foo.cpp &&./a.out | c++filt”, I get something like this:

./a.out(bar(int, float)+0x10)[0x8048a0a]

Note that without -rdynamic the function name symbols won’t be available. Anyway, what we get is much more interesting than raw pointers. And exactly what we were looking for. It’s also very boring, unless we learn what’s going on inside backtrace_symbols_fd. If we go and check what backtrace_symbols_fd is doing (sysdeps/generic/elf/backtracesyms.c in glibc) we’ll see that all the heavy work is done by libdl. A quick check with ‘man dladdr’ will show that we are on the right path. Let’s add this to our program:

#include <dlfcn.h>
int get_sym_name(void *addr) {
    Dl_info info;
    int res = dladdr(addr, &info);
    cout << info.dli_fname << ": " << info.dli_sname << endl;

Behold, we now have a nice backtrace in C++, not so different than the bt you’d get in any dynamic language:

./a.out: _Z3barif
./a.out: main
/lib/i386-linux-gnu/ __libc_start_main

Turtles all the way down

Getting the function name using libdl feels a bit like cheating, after we manually walked the call stack. They are not in the same level of abstraction. Can we check what lurks inside libdl’s dladdr? It’s absolutely possible. In theory. Now we are dealing not only with a specific architecture (x86) we are also dealing with a binary format (more specifically, elf). To understand what goes on inside libdl’s we need to know about the runtime linking process and elf internals. Feel free to peek at glibc/dlfcn/dlinfo.c, but beware that’s a daunting task, way beyond the original scope of this article.

Epilogue / Disclaimer

The whole series on getting a stacktrace on C++ is merely “educational”, as in “never-ever do this on your program”. As stated on the first part of the series it’s not portable, and it’s also extremely frail. If you want something production ready use glibc’s backtrace features. And if you want something portable, try libunwind. It works great, but where would the fun be if we skipped the whole learning process and went straight to this library?

Getting a stacktrace on C/C++: Mapping function pointers to function names in obj files

Last time we saw how to get a stacktrace in C++, yet we only had access to the list of function pointers and not to the function names. Still, pointers are not that useful. Can we get function names instead? Yes, we can but it’s not easy. One option would be to read the elf specification. Boring. Let’s tinker around with our test program, may be we can find something interesting:

    Caller *caller = (Caller*)sp;
    while (caller) {
        cout << caller->addr << endl;
        void** foo = (void**)caller;
        cout << "\t" << foo[0] << "|" << foo[1] << endl;
        caller = caller->addr;

On my machine I got something like this:


The first address is the memory address of the stack to which we should return after executing this function. The second address looks interesting. It looks like the addresses we see when dissasemblying an object. Let’s try running ‘objdump -Sd ./a.out’:

08048ac0 <_Z3barif>:
 8048ac0: 55                      push   %ebp
 8048ac1: 89 e5                   mov    %esp,%ebp
 8048ac3: 83 ec 08                sub    $0x8,%esp
 8048ac6: e8 e1 fe ff ff          call   80489ac &lt;_Z3foov&gt;
 8048acb: c9                      leave
 8048acc: c3                      ret

08048acd :
 8048acd:   55                      push   %ebp
 8048ace:   89 e5                   mov    %esp,%ebp
 8048ad0:   83 e4 f0                and    $0xfffffff0,%esp
 8048ad3:   83 ec 10                sub    $0x10,%esp
 8048ad6:   b8 00 00 00 40          mov    $0x40000000,%eax
 8048adb:   89 44 24 04             mov    %eax,0x4(%esp)
 8048adf:   c7 04 24 02 00 00 00    movl   $0x2,(%esp)
 8048ae6:   e8 d5 ff ff ff          call   8048ac0 &lt;_Z3barif&gt;
 8048aeb:   b8 00 00 00 00          mov    $0x0,%eax
 8048af0:   c9                      leave
 8048af1:   c3                      ret

And, indeed, 0x8048acb and 0x8048aeb are both there: they are the EIP after the ret call! Note that you may use c++filt if the mangled names are too confusing. Anyway, we can indeed get the function names, albeit in a rather contrived way. Is there a better way to get a backtrace and its symbols’ names? Turns out there is and we’ll see how to get a function’s name during runtime, in the next article.

Getting a stacktrace on C/C++: Some calling internals

High level languages tend to have a lot of features for introspection and metaprogramming. One of those useful features is the possibility to get a stacktrace of the current function. At first C++ would seem to lack that ability but once you think about it, high level languages internal workings are in the very basics not that different from lower level languages: they tend to be a virtual representation of the physical hardware. A function call, in the end, will most likely be implemented the same on both C++ and Ruby. So, although it may not be as straight forward as it is with a dynamic language, we should be able to get a stacktrace just fine. Also, there’s a big clue for us: gdb can get stacktraces just fine, so why wouldn’t we?

Let’s start by trying to figure out how we can get a stacktrace by ourselves, with no help of any other tools. Sounds like a daunting task? It isn’t really. Let’s write a simple program to figure out how gcc performs function calls:

int foo() {
    return 42;

void bar() {

int main() {
    return 0;

If we compile this with gcc -S we’ll get a .s file with the disassembly. Of course this depends a lot on the compiler, architecture, OS, etc, etc. For the moment we’ll just assume x86 gcc Linux with no optimizations. A lot of the code from the disassembly will be part of the compiler’s preamble and postamble. Cleaning things up a bit we should see something like this:

	pushl	%ebp
	movl	%esp, %ebp
	call	_Z3foov
	popl	%ebp

Doesn’t look so hard: it just pushes the current stack base pointer to the stack, sets a new stack pointer and calls the function (you might want to play around with c++filt if name mangling confuses you). Once it returns it just reads back the original stack base pointer and continues. Knowing that return addresses are in the stack makes it easy for us to retrieve this information, we just need a way to get the current stack pointer. Some assembler in C++ will be needed:

    void *sp;
    asm("movl %%esp,%0"; : "=r"(sp));
    std::cout << sp << std::endl;

That should print the current function’s start address. But from our disassembly we can also see that the current function’s return address, ie its caller, would be stored in the first word of the current function’s stack. Likewise, our caller’s return address will be on its first stack word. Let’s check if this holds up in the code:

    void *sp;
    asm("movl %%esp,%0"; : "=r"(sp));
    void *caller_addr = *(void**)sp;
    void *caller_addr2 = *(void**)caller_addr;
    void *caller_addr3 = *(void**)caller_addr2;

    cout << sp &lt;&lt; endl;
    cout << caller_addr << endl;
    cout << caller_addr2 << endl;
    cout << caller_addr3 << endl;

Looks ugly, but remember we are fighting the type system here: we need to tell the compiler that the void* we’re trying to access is actually a void**. We’ll clean that up later, for the moment if we run that on our sample we should see all the stack addresses that for our stack trace, ending with a null pointer for the main function. Pretty neat, huh? So far we only have function addresses, but we’ll get some pretty names later. Let’s make it a bit more generic before moving on.

    struct Caller {
            Caller *addr;

    // Get the stack base ptr from a register
    void *sp;
    asm(&quot;movl %%ebp,%0&quot; : &quot;=r&quot;(sp));

    // Loop through every caller
    Caller *caller = (Caller*)sp;
    while (caller) {
        cout &lt;&lt; caller-&gt;addr &lt;&lt; endl;
        caller = caller-&gt;addr;

Of course this is very naive, as it will only work on a 32 bit platform, and it will break as soon as we change calling conventions, but it’s still useful to draw some conclusions:

  • Getting a stacktrace in C++ is indeed possible
  • Now we know why inlined functions and optimizations make debugging more difficult (hint: how can you get a stack frame for a function that doesn’t really exist?)

Next time we’ll see how we can get a function name from it’s pointer.

Faking a server and testing networks with netcat

Not long ago I wrote about having to use iptables to redirect packets from one port to another. Testing this with a real server may be complicated, or at least inconvenient. Luckily we have netcat to help us.

If you use “nc -l 1234”, netcat will create a listening socket on the port 1234. You can check if it’s working by doing a “telnet IP 1234”, nc should echo whatever you type on the client in the server. In the example from my article explaining an iptables rule, you would do an nc -l 1234, apply the iptables rule and the issue a “netcat IP 4321”. If everything went according to plan you should be seeing the echo on your nc server.

gdb pretty printers

If you have ever used gdb then you know printing an stl object is useless. You’ll be flooded with stuff you don’t care about, and if you want to find, say, the contents of an std::vector you’ll have to dive through tons of junk. It turns there’s an easier way, it’s called pretty printers and I have no idea why they are not included by default with gdb.

You’ll need to download the pretty printers at svn co svn:// and then create a ~/.gdbinit like this one:

import sys
sys.path.insert(0, '~/gdb_prettyprinters/python')
from libstdcxx.v6.printers import register_libstdcxx_printers
register_libstdcxx_printers (None)

Have fun!