Alberto Simoes (via RT) wrote:
Sorry for sending the details this way, but to reorganizing these emails
would take too much time :)
[ Please don't top-post and cite only necessary parts during a f'up. ]
I've checked in a change (r9507) that hopefully fixes this bug (libgdbm
was loaded twice)
# New Ticket Created by Alberto Simoes
# Please include the string: [perl #37462]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37462 >
Sorry for sending the details this way, but to reorganizing these emails
would take
Well, here goes a stupid patch. Just removes the fprintf to the stderr.
If the function returns NULL on failure, callers should verify result.
Can't remember the name of someone who suggested right this. I just
needed to look a little more to the code to be sure it was the right(??)
thing to d
Ok, more details on this bug...
on src/dynext.c...
PMC *Parrot_init_lib(Interp *interpreter,
PMC *(*load_func)(Interp *),
void (*init_func)(Interp *, PMC *))
{
PMC *lib_pmc = NULL;
fprintf(stderr, "Called..\n");
if (load_func)
lib_pmc = (*load
Always the last one. For each test, the get_path is called twice and in
both cases the third printf is the one called.
Cheers
Alberto
Bernhard Schmalhofer wrote:
Alberto Simões schrieb:
It's me again. Linked with gdbm (compiled with fink) and got these
errors.
They are kind weird because t
gdbmhash.pmc class_init is being called more than once... first time the
load fails, second time it fails... and is not called any more.
Something very weird around :)
Alberto Simões wrote:
It's me again. Linked with gdbm (compiled with fink) and got these errors.
They are kind weird because
Alberto Simões schrieb:
It's me again. Linked with gdbm (compiled with fink) and got these
errors.
They are kind weird because they complain about not being able to load
the library, but the tests run correctly. If they run correctly
without loading the library one of two things happens:
1
It's me again. Linked with gdbm (compiled with fink) and got these errors.
They are kind weird because they complain about not being able to load
the library, but the tests run correctly. If they run correctly without
loading the library one of two things happens:
1) the tests do not test the
