[Openmcl-devel] Troubleshooting FFI calls on ARM

[Jeremy Shoemaker]

> One suggestion: use %get-signed-long to read out a few bytes of memory at
the location reported by (external "getpid”) and then write a little C
program that does the same thing and see if you get the same result.

I'm not sure I entirely follow, at least the C program part. Are you
suggesting peeking at the memory pointed to by the `getpid` function in C?
I'm not quite sure how to do that, but my C is pretty rusty.

On Wed, Jun 19, 2019 at 3:52 PM Ron Garret <ron at flownet.com> wrote:

>
> On Jun 19, 2019, at 1:45 PM, Jeremy Shoemaker <jeremy at codingkoi.com>
> wrote:
>
> > I've tried using (external "getpid"), and I get back the addresses of
> the external-entry-point for getpid and lib.so.6 but I'm not sure how to
> confirm if those are pointing to the right locations.
>
> One suggestion: use %get-signed-long to read out a few bytes of memory at
> the location reported by (external "getpid”) and then write a little C
> program that does the same thing and see if you get the same result.
>
> > I realize this is probably some esoteric configuration that I'm trying
> to play around with, and that here may be dragons, but any help would be
> greatly appreciated.
>
> IMHO this is something one should reasonably be able to expect to work.
>
> rg
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20190619/7ca0b6f5/attachment.htm>