public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 12/14] add linux_infcall_mmap
Date: Tue, 11 Nov 2014 16:43:00 -0000	[thread overview]
Message-ID: <54623CA7.8060702@redhat.com> (raw)
In-Reply-To: <20141101214719.13230.96367.stgit@host1.jankratochvil.net>

On 11/01/2014 09:47 PM, Jan Kratochvil wrote:
> +/* See gdbarch.sh 'infcall_mmap'.  */
> +
> +static CORE_ADDR
> +linux_infcall_mmap (CORE_ADDR size, unsigned prot)
> +{
> +  struct objfile *objf;
> +  /* Do there still exist any Linux systems without "mmap64"?
> +     "mmap" uses 64-bit off_t on x86_64 and 32-bit off_t on i386 and x32.  */
> +  struct value *mmap_val = find_function_in_inferior ("mmap64", &objf);
> +  struct value *addr_val;
> +  struct gdbarch *gdbarch = get_objfile_arch (objf);
> +  CORE_ADDR retval;
> +  enum
> +    {
> +      ARG_ADDR, ARG_LENGTH, ARG_PROT, ARG_FLAGS, ARG_FD, ARG_OFFSET, ARG_MAX
> +    };
> +  struct value *arg[ARG_MAX];
> +
> +  arg[ARG_ADDR] = value_from_pointer (builtin_type (gdbarch)->builtin_data_ptr,
> +				      0);
> +  /* Assuming sizeof (unsigned long) == sizeof (size_t).  */
> +  arg[ARG_LENGTH] = value_from_ulongest
> +		    (builtin_type (gdbarch)->builtin_unsigned_long, size);
> +  gdb_assert ((prot & ~7) == 0);
> +  arg[ARG_PROT] = value_from_longest (builtin_type (gdbarch)->builtin_int,
> +				      0
> +				      | ((prot & 4) != 0 ? PROT_READ : 0)
> +				      | ((prot & 2) != 0 ? PROT_WRITE : 0)
> +				      | ((prot & 1) != 0 ? PROT_EXEC : 0));
> +  arg[ARG_FLAGS] = value_from_longest (builtin_type (gdbarch)->builtin_int,
> +				       MAP_PRIVATE | MAP_ANONYMOUS);

PROT_READ, PROT_WRITE, PROT_EXEC, MAP_PRIVATE, MAP_ANONYMOUS
are host values/macros.

This needs to be made host independent, otherwise cross debugging to
Linux passes the wrong values to mmap.

It also likely breaks --enable-targets=all builds on hosts
that don't have mmap at all.  E.g., this comes out empty on F20:

 $ grep -rn PROT_READ /usr/i686-w64-mingw32/sys-root/mingw/include/

OTOH, the 4, 2 and 1 bits checked against the 'prot' argument
are magical constants; they'd best be put behind macros, like e.g.,
GDB_MMAP_PROT_READ, etc., here and at the callers
of gdbarch_infcall_mmap.

Thanks,
Pedro Alves

  reply	other threads:[~2014-11-11 16:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 21:45 [PATCH v3 00/14] let gdb reuse gcc's C compiler Jan Kratochvil
2014-11-01 21:46 ` [PATCH v3 03/14] add some missing ops to DWARF assembler Jan Kratochvil
2014-11-01 21:46 ` [PATCH v3 07/14] add gnu_triplet_regexp gdbarch method Jan Kratochvil
2014-11-01 21:46 ` [PATCH v3 02/14] add gcc/gdb interface files Jan Kratochvil
2014-11-03 12:51   ` Yao Qi
2014-11-03 12:56     ` Jan Kratochvil
2014-11-03 13:24       ` Yao Qi
2014-11-01 21:46 ` [PATCH v3 08/14] introduce call_function_by_hand_dummy Jan Kratochvil
2014-11-01 21:46 ` [PATCH v3 06/14] add infcall_mmap and gcc_target_options gdbarch methods Jan Kratochvil
2014-11-01 21:46 ` [PATCH v3 04/14] add make_unqualified_type Jan Kratochvil
2014-11-01 21:46 ` [PATCH v3 05/14] add dummy frame destructor Jan Kratochvil
2014-11-01 21:46 ` [PATCH v3 01/14] introduce ui_file_write_for_put Jan Kratochvil
2014-11-01 21:47 ` [PATCH v3 11/14] export dwarf2_reg_to_regnum_or_error Jan Kratochvil
2014-11-01 21:47 ` [PATCH v3 12/14] add linux_infcall_mmap Jan Kratochvil
2014-11-11 16:43   ` Pedro Alves [this message]
2014-11-23 19:11     ` Jan Kratochvil
2014-12-12 14:38       ` Pedro Alves
2014-11-01 21:47 ` [PATCH v3 09/14] split dwarf2_fetch_cfa_info from dwarf2_compile_expr_to_ax Jan Kratochvil
2014-11-01 21:47 ` [PATCH v3 10/14] make dwarf_expr_frame_base_1 public Jan Kratochvil
2014-11-01 21:47 ` [PATCH v3 13/14] add s390_gcc_target_options Jan Kratochvil
2014-11-01 21:48 ` [PATCH v3 14/14] the "compile" command Jan Kratochvil
2014-11-02 16:03   ` Eli Zaretskii
2014-11-20 21:24     ` Jan Kratochvil
2014-11-21  7:58       ` Eli Zaretskii
2014-11-21 18:41         ` Jan Kratochvil
2014-11-21 19:47           ` Eli Zaretskii
2014-11-03 13:08   ` Yao Qi
2014-11-14 18:43     ` Jan Kratochvil
2014-11-11 18:53   ` Pedro Alves
2014-11-23 18:36     ` Jan Kratochvil
2014-12-12 14:38       ` Pedro Alves
2014-11-01 21:52 ` [PATCH v3 00/14] let gdb reuse gcc's C compiler Jan Kratochvil
2014-11-01 21:56 ` Jan Kratochvil
2014-11-03 12:47 ` Yao Qi
2014-11-03 12:49   ` Jan Kratochvil

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=54623CA7.8060702@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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).