crash - seen this before? cant' find bugs FAQ

  • John D. Hendrickson

    FIRST. HEY. Google news is shut down (wash dc, usa, 404). My
    service provider blocks nntp and also shut down their nntp server
    (also block my mail server). (infact i see a regular progression of
    microsoft/cox shutting down what linux people are using). think about
    using majordomo or html please.

    have you seen the below before ? also I can't find any "known bugs
    for ..." in FAQ so i ask. likely my only ever question :)

    for 3D, textcolor.dem:# Textcolor in 3D (req. pm3d) does work.

    But for all other 3D .dem examples (ie, world.dem when it tries to do
    3D) I get:

    Hit return to continue
    gnuplot: malloc.c:3097: sYSMALLOc: Assertion `(old_top == (((mbinptr)
    (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct
    malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size)

    = (unsigned long)((((__builtin_offsetof (struct malloc_chunk,
    fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t)))
    - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end &
    pagemask) == 0)' failed.

    what am i up against? should i assume i can't use the debian pkg and
    get source? should I assume i have an os problem to trace down?

    I'm running Debian/Sarge and fresh install of gnuplot. I seem to
    remember the 3D examples never worked on any sarge install on this
    side but am unsure. In general I have no problems with other
    softwares excep t firefox of course.

    and against, really, thanks for a long legacy of great gs x11 et al

  • Ethan Merritt

    Ethan Merritt - 2013-07-12

    Google's working here; I can't offer any help with your service provider.
    If you need a free nntp feed, try

    What version of gnuplot are you running?
    (Debian Sarge is ancient, right? isn't this 5 years past it's use-by date?)

    I am not aware of any current or past generic problems with memory allocation in the 3D code. The dump you show is not from gnuplot code. It's from a system routine. Without some hint of where in gnuplot it was called from I don't see any hope of debugging it. Anyhow, there's no point in debugging an ancient version. If you can reproduce the problem against a reasonably recent gnuplot (4.6 was released in 2012) it'll get a lot more attention.


Log in to post a comment.