invalid pointer

User 2174 | 8/18/2015, 1:44:48 AM

download GraphLab-Create-1.5.2.tar.gz from, install as usual python install

try sample script from dato-code/how-to python * glibc detected python: free(): invalid pointer: 0x00007f3b355ab4c0 ** ======= Backtrace: =========

glibc incompatibile? ldd --version ldd (Ubuntu EGLIBC 2.15-0ubuntu10.12) 2.15 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Roland McGrath and Ulrich Drepper.

Appreciate if anyone can help with this issue.

what is the difference between graphlab-create from pypi and the one from dato website that needs to register?


User 954 | 8/18/2015, 4:45:29 PM

Hello, sorry for the inconvenience.

GLC in pypi and the one on the website are the same thing. The website has instructions of how to install GraphLab from pypi. You need to register to our website to get a license key. The license is required to run any GraphLab function. We have 30 days free trial and we are free for academic usage.

If the problem exist after you install GraphLab following the instructions on the website, then please provide us with the following information:

  • What is the python installation your system has?
  • What is your operating system?
  • Did you try GraphLab on some virtual environment? (virtualenv or Conda)

Thanks, Emad

User 15 | 8/18/2015, 6:24:53 PM


This error message does not look like an incompatible glibc. We have tested on systems with glibc older than 2.15 and GLC works. It looks like somewhere we are freeing an invalid pointer, and glibc detected it (thanks for providing that info though). Is a backtrace printed out, or is it left blank like in your message? Even addresses with no symbol information in the backtrace would help us to debug this.

Also, does this happen immediately when you run the dimsum script, or is it after a large amount of time? Does the system's memory fill up? Not knowing how much time passed between the script start and the error, this could be due to memory pressure.