Re: New bug :-( Re: Release plan for gnuplot 4.0

[Hans-Bernhard B. <br...@ph...>]

On Fri, 20 Feb 2004, Ethan Merritt wrote:

> I am pretty sure that the negative values are themselves a
> result of some upstream error that I haven't found yet.
> Maybe someone else can spot it?

Here's what's happening (using the X11 terminal for simplicity, and
a conditional break point on negative results in map_position()):

#0  map_position (pos=0x810f028, x=0xbfffe49c, y=0xbfffe4a0,
    what=0x80ed754 "key") at ../../src/graphics.c:3813
#1  0x08065c8f in boundary (plots=0x812a738, count=2)
    at ../../src/graphics.c:909
#2  0x080666d1 in do_plot (plots=0x812a738, pcount=2)
    at ../../src/graphics.c:1189
#3  0x080850c4 in eval_plots () at ../../src/plot2d.c:1616
#4  0x08050d88 in command () at ../../src/command.c:511
#5  0x08050959 in do_line () at ../../src/command.c:368

(gdb) info loc
x = (unsigned int *) 0xbfffe49c
y = (unsigned int *) 0xbfffe4a0
xx = -13.5
yy = -4067.5

That call's coming from here:

907             } else {
908                 unsigned int x, y;
909                 map_position(&key->user_pos, &x, &y, "key");

followed immediately by the somewhat suspicious:

910     #if 0
911     /* FIXME!!!
912     ** pm 22.1.2002: if key->user_pos.scalex or scaley == first_axes 
or seco
...

-- 
Hans-Bernhard Broeker (br...@ph...)
Even if all the snow were burnt, ashes would remain.