public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: Richard Henderson <rth@redhat.com>, libffi-discuss@sourceware.org
Subject: Re: *printf functions
Date: Sat, 25 Apr 2015 17:31:00 -0000	[thread overview]
Message-ID: <553BCF7A.8030502@gmail.com> (raw)
In-Reply-To: <553AD0A8.2040602@redhat.com>

On 04/24/15 16:24, Richard Henderson wrote:
> On 04/24/2015 11:54 AM, Bruce Korb wrote:
>> Is my hope to use libffi for calling snprintf a vein one?
>
> As long as you used ffi_prep_cif_var instead of ffi_prep_cif it will work.  You
> didn't quote enough of your source to see that part.

OK, here's the more complete debug session:

148             ffi_type ** args = assemble_ffi_args(evd, edsc, &values);
(gdb) n
153             values[0] = buf;
(gdb)
154             args[0]   = &ffi_type_pointer;
(gdb)
156             values[1] = &spc;
(gdb)
157             args[1]   = (sizeof(size_t) == sizeof(u64))
(gdb)
160             values[2] = UNCONST(ev_fmt);
(gdb)
161             args[2]   = &ffi_type_pointer;
(gdb)
163             if (ffi_prep_cif_var(&cif, FFI_DEFAULT_ABI, 3, edsc->edsc_argct + 3,
(gdb)
167                     ffi_call(&cif, fn, &ret_val, values);
(gdb) p cif
$1 = {abi = FFI_UNIX64, nargs = 5, arg_types = 0x8710510,
   rtype = 0x613dd0 <ffi_type_uint32>, bytes = 0, flags = 9}
(gdb) p cif.arg_types[0]
$2 = (ffi_type *) 0x613db0 <ffi_type_pointer>
(gdb) p cif.arg_types[1]
$3 = (ffi_type *) 0x613d90 <ffi_type_uint64>
(gdb) p cif.arg_types[2]
$4 = (ffi_type *) 0x613db0 <ffi_type_pointer>
(gdb) p cif.arg_types[3]
$5 = (ffi_type *) 0x613dd0 <ffi_type_uint32>
(gdb) p cif.arg_types[4]
$6 = (ffi_type *) 0x613dd0 <ffi_type_uint32>
(gdb) p (char *)values[0]
$7 = 0x7fffffffc6b4 ""
(gdb) p *(unsigned long *)values[1]
$8 = 4044
(gdb) p (char *)values[2]
$9 = 0x40fe70 "Allocated sblock_id=%d for band_id=%d"
(gdb) p *(unsigned *)values[3]
$10 = 1
(gdb) p *(unsigned *)values[4]
$11 = 1
(gdb) p fn
$12 = (void *) 0x4012d0 <snprintf@plt>

So I put together the "var" portion of the arg list with "assemble_ffi_args()" and upon
return insert the three fixed args (destination, size and format string).
I've printed out the "cif", the arg types and the arg values and they all look correct.
I will now press "n" and "<enter>" and have a seg fault:

> (gdb) n
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7455892 in vsnprintf () from /lib64/libc.so.6

:(  This would make for a perfect example for the use of ffi_prep_cif_var() :)

> (gdb) bt
> #0  0x00007ffff7455892 in vsnprintf () from /lib64/libc.so.6
> #1  0x00007ffff7433ff2 in snprintf () from /lib64/libc.so.6
> #2  0x00007ffff7796cd8 in ffi_call_unix64 () from /usr/lib64/libffi.so.4
> #3  0x00007ffff7796729 in ffi_call () from /usr/lib64/libffi.so.4

P.S. I also have a /usr/local/lib64/libffi.a built with "-O0 -ggdb3 -gdwarf-2",
if more debugging stuff is useful.

> Breakpoint 1, format_one_event (buf=0x7fffffffc6b4 "", spc=4044,
>     fn=0x401250 <snprintf@plt>, evd=0x7ffff5ecc088,
>     ev_fmt=0x411630 "Allocated sblock_id=%d for band_id=%d",
>     edsc=0x615a98 <event_data_for_sblock+56>) at evt/src/event-print.c:148
> 148             ffi_type ** args = assemble_ffi_args(evd, edsc, &values);
> (gdb) c
> Continuing.
>
> Breakpoint 2, ffi_call_unix64 () at ../src/x86/unix64.S:49
> 49              movq    (%rsp), %r10            /* Load return address.  */

      reply	other threads:[~2015-04-25 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-24 21:54 Bruce Korb
2015-04-24 23:24 ` Richard Henderson
2015-04-25 17:31   ` Bruce Korb [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=553BCF7A.8030502@gmail.com \
    --to=bruce.korb@gmail.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=rth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).