From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Chris Faylor <cgf@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: strip stdcall suffixes under Cygwin
Date: Wed, 27 Mar 2002 15:49:00 -0000 [thread overview]
Message-ID: <20020327184904.A22189@nevyn.them.org> (raw)
In-Reply-To: <20020327233525.1164E5EA11@zwingli.cygnus.com>
On Wed, Mar 27, 2002 at 06:35:25PM -0500, Jim Blandy wrote:
>
> Chris, I think I need your approval for this.
>
> 2002-03-27 Jim Blandy <jimb@redhat.com>
>
> * config/i386/tm-cygwin.h: #define
> LINKER_SYMBOLS_HAVE_WIN32_STDCALL_ARG_SIZES.
> * symtab.c (LINKER_SYMBOLS_HAVE_WIN32_STDCALL_ARG_SIZES): Provide
> default #definition here, if tm-*.h file doesn't have one.
> (symbol_init_mangled_name): If the above is #defined, strip off
> the stdcall arg size, if present, from linker symbol names before
> trying to demangle them.
> + if (LINKER_SYMBOLS_HAVE_WIN32_STDCALL_ARG_SIZES)
> + {
> + char *arg_byte_suffix = strchr (mangled, '@');
> + if (arg_byte_suffix)
> + {
> + int prefix_len = arg_byte_suffix - mangled;
> + char *mangled_sans_suffix = alloca (prefix_len + 1);
> + memcpy (mangled_sans_suffix, mangled, prefix_len);
> + mangled_sans_suffix[prefix_len] = '\0';
> +
> + mangled = mangled_sans_suffix;
> + }
> + }
> +
Perhaps verify that you are stripping off a number?
(ELF uses @ for representing symbol versions also.)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-27 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 15:35 Jim Blandy
2002-03-27 15:48 ` RFA: strip stdcall suffixes under cygwin Christopher Faylor
2002-03-27 15:49 ` Daniel Jacobowitz [this message]
2002-03-27 15:50 ` RFA: strip stdcall suffixes under Cygwin Andrew Cagney
2002-03-27 17:59 ` Andrew Cagney
2002-03-27 19:42 ` RFA: strip stdcall suffixes under cygwin Christopher Faylor
2002-03-27 20:05 ` Andrew Cagney
2002-03-27 20:09 ` Christopher Faylor
2002-03-27 20:22 ` Andrew Cagney
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=20020327184904.A22189@nevyn.them.org \
--to=drow@mvista.com \
--cc=cgf@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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