Wed Dec 03 09:50:27 2014: Request 100686 was acted upon.
Transaction: Correspondence added by RSCHUPP
       Queue: PAR-Packer
     Subject: Window executable crashes when including Wx::Html in PAR::PACKER 
build
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: davwo...@cisco.com
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=100686 >


Am 2014-12-03 09:11:01, davwo...@cisco.com schrieb:
> From ActiveState.

OK, that explains

> By the way, your comment " These two -l options shouldn't be necessary." Is 
> not true. See the attached screenshot.

because your wx stuff looks like it's built using the Mingw32 toolchain
(ActiveState build their stuff with Microsoft VisualStudio). 
But this shouldn't be relevant for your problem.

It would be interesting to know what "real" name of the DLL that's mentioned
in your screenshot (3cbfbb3e.dll) is - PAR::Packer extracts (glue) DLLs
from the packed executable not with their original names, but with 
a mangled one (IIRC the CRC32 checksum of the file).

Try to find this DLL on your disk, it should be located below a directory
named par-XXXXXXX in the "temp" directory of your Windows environment
(e.g check environment variables TEMP or TMP).

Then run

objdump -ax your.dll | grep Name           (or Windows equivalent of grep)

Should print something like:

                 Table   Stamp     Chain    Name      Thunk
        DLL Name: cygwin1.dll                               <---
        vma:  Hint/Ord Member-Name Bound-To
        DLL Name: KERNEL32.dll                              <---
        vma:  Hint/Ord Member-Name Bound-To
        DLL Name: cygperl5_14.dll                           <---
        vma:  Hint/Ord Member-Name Bound-To
Name                            000000000000803c Clone.dll  <===
        [Name Pointer/Ordinal] Table    00000002
        Name Pointer Table              0000000000008030

where <=== marks the "real" name and the <--- mark the DLLs referenced
(linked) from this DLL.


Cheers, Roderich

Reply via email to