> We tried this here (upstream) with 2.2.1 on i686, and with latest CVS on
> x86_64,
> and we don't get the segfault but we do get:
interesting. but I use 32bit machine, you seem to use 64bit
architecture, doesn't it imply 64bit pointers and/or different memory
alignment? i.e. you just might be ou
marius mikucionis wrote:
We tried this here (upstream) with 2.2.1 on i686, and with latest CVS on
x86_64,
and we don't get the segfault but we do get:
interesting. but I use 32bit machine, you seem to use 64bit
architecture, doesn't it imply 64bit pointers and/or different memory
alignmen
Marius Mikucionis wrote:
Package: graphviz
Version: 2.2.1-1
Severity: important
Not sure whether it is connected to 305375, but I don't know how to work
arround the segfault, it's very anoying and I can't work with it.
obviously there is memory mishandling somewhere.
valgrind can locate the il
Package: graphviz
Version: 2.2.1-1
Severity: important
Not sure whether it is connected to 305375, but I don't know how to work
arround the segfault, it's very anoying and I can't work with it.
obviously there is memory mishandling somewhere.
valgrind can locate the illegal segment read in the co
4 matches
Mail list logo
