which is quite obvious since gs is NULL. Walking back through the stack trace and looking through the code, this gs instance is supposed to be set in spectre_exporter_pdf_begin() with a spectre_gs_new() call.
It looks like this amd64 crash is a logic error and unrelated to the libspectre crash that you see (which should be fixed in any case, but perhaps in a separate bug report)?
On current lucid amd64, I get
#0 spectre_gs_process (gs=0x0, filename= 0x7f75d400a720 "/tmp/ecrs.ps", x=0, y=0, begin=406, end=319212) gs_send_ page (gs=0x0, doc=0x7f75d400be80, page_index=1, x=0, y=0) exporter_ pdf_do_ page (exporter= 0x7f75e9499460, page_index=0) exporter- pdf.c:71
at spectre-gs.c:91
#1 0x00007f75d9ae71e1 in spectre_
at spectre-gs.c:241
#2 0x00007f75d9ae8717 in spectre_
at spectre-
which is exactly the same as the original stack trace reported here. Looking at the code, this crashes in
void *ghostscript_ instance = gs->ghostscript _instance;
which is quite obvious since gs is NULL. Walking back through the stack trace and looking through the code, this gs instance is supposed to be set in spectre_ exporter_ pdf_begin( ) with a spectre_gs_new() call.
It looks like this amd64 crash is a logic error and unrelated to the libspectre crash that you see (which should be fixed in any case, but perhaps in a separate bug report)?