I am trying to run https://github.com/seanpringle/simpleswitcher on my ubuntu 12.04

I downloaded it and compiled it. However, when I run I get

*** glibc detected *** ./simpleswitcher: free(): invalid next size (fast): 0x08bff5a8 ***
======= Backtrace: =========
======= Memory map: ========
00110000-002b3000 r-xp 00000000 08:04 424359     /lib/i386-linux-gnu/libc-2.15.so
(memory map goes on and on)

how can I figure out what is going on ? what are some hypotesis I should consider ? How do I start trying to figure this out ?

I am a programmer -to say, I can write simple C and python- but I frankly have no idea what is going on

  • 1
    Try from this branch/fork github.com/DaveDavenport/simpleswitcher , I looked at the pull reuests and one had a "fixed ubuntu build" commit, might be worth a shot – Mateo May 30 '13 at 1:32
  • well, what do you know ... It works. I though I needed to learn gdb today. Apparently, I needed git =P – josinalvo May 30 '13 at 1:46
  • cool. I am still curious about how I would debug the program, so I am not closing the question yet. But yes. Make it an answer so that I can give you an upvote – josinalvo May 30 '13 at 1:55
  • Some others might know more about tracing errors, a paste of the full error may help on paste.ubuntu.com – Mateo May 30 '13 at 2:07

In looking at the "Issues" or "Pull Requests" one of the pull requests labeled "small updates" has a commit that says:

Martijn Koedam        Fix building ubuntu          6d0f4a9 

But in the comment section of that pull, It looks like the author decided to "Cherry Pick" only part of the commits, excluding some Distribution specific changes saying:

Some simpleswitcher users run limited versions of make (eg, bmake) which the current crude Makefile supports.

This leads me to believe that it might work on Ubuntu with this commit (commit was about 4 months ago).

So try building with this fork, as it looks like they are targeting some distribution specific issues: https://github.com/DaveDavenport/simpleswitcher

| improve this answer | |
  • I figured it out! It was just a malloc error. Thanks for the initial push – josinalvo May 30 '13 at 20:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.