On Wed Sep 10 08:12:59 2008, julianalbo wrote: > > I've recently commited a fix on null string constants. I think it was > > the same problem described here. I compiled the pir file and pdumped > > without a problem, it shows the DATA => NULL my fix introduced. > > > > Can you verify the problem is gone? > > > > I assume you are referring to r30756 of src/packdump.c? Yes, that does > > avoid the segfault (though it reports the string value as "NULL" instead > > of "''"). But isn't this really a bug in PIO_printf handling of "%.*s"?
If the segfault is avoided, can we close out this RT and open a trac ticket for any remaining fixables? > The NULL is my fault, I put it that way for easy searchability while > testing. You are right, the value is an empty string and must be > reported like that. > > The printf-alike parrot functions seem to have a problem with NULL c > strings, yes, we will solve this quickly (I hope). > > But printf-alikes can't know the NULL is really a parrot empty string, > because we dropped that information by the fact of passing a c string > instead of the parrot string. So I think the correct solution will be > to stop accessing string internals and using the parrot strings api. > > In the meantime, what we need to know now in this ticket is if the > segfault is no longer present in all platforms reported. > -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
