The target= argument is parsed out of the python tuple for the open calls, but then is ignored as you explicitly pass in NULL to the target fields of bfd_openr and bfd_fdopenr. Is there a reason for this or is this a minor bug? If its a bug, you might want to fix (I don't see the need to do a whole pull request for such a trivial fix, but will if you'd like me to anyway).
This used to work fine for me, but recently the libbfd autodetection started to fail for certain 32-bit arm targets, so I needed to pass in the explicit target type, and discovered that wasn't working.
Cheers
The target= argument is parsed out of the python tuple for the open calls, but then is ignored as you explicitly pass in NULL to the target fields of bfd_openr and bfd_fdopenr. Is there a reason for this or is this a minor bug? If its a bug, you might want to fix (I don't see the need to do a whole pull request for such a trivial fix, but will if you'd like me to anyway).
This used to work fine for me, but recently the libbfd autodetection started to fail for certain 32-bit arm targets, so I needed to pass in the explicit target type, and discovered that wasn't working.
Cheers