From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Cc: "Ecos-List (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Redboot and builtin functions
Date: Thu, 19 Oct 2000 03:31:00 -0000 [thread overview]
Message-ID: <20001019123121.Q474@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <5AF611D83988D4118ACF00E0B10400540557D1@mr-intranet.sdesigns.net>
> About builtins functions, memcpy, memset ...
>
> I've seen that memset and memcpy are defined and implemented in multiple
> places.
>
> One of this place is generic-stub.c where a comment says that the stub can't
> use the same memcpy and memset than the rest (I can't see really why but why
> not..)
We had a problem where we needed to single step through memcpy when we
had some data corruption going in. The gdb stub itself uses memcpy, so
you end with a break point in the code handling the break point and it
all dies horribly. The static definitions of memcpy in the stub make
sure the stub has its own memcpy functions which will never get a
break point in it and you can then debug the globel memcpy functions.
Andrew
next prev parent reply other threads:[~2000-10-19 3:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-19 1:52 Fabrice Gautier
2000-10-19 3:31 ` Andrew Lunn [this message]
2000-10-19 4:02 ` Jesper Skov
2000-10-19 6:13 ` Jonathan Larmour
2000-10-19 5:01 ` Bart Veer
2000-10-19 6:24 ` Gary Thomas
2000-10-19 6:48 ` Bart Veer
-- strict thread matches above, loose matches on Subject: below --
2000-10-19 11:02 Fabrice Gautier
2000-10-19 11:28 ` Bart Veer
2000-10-18 21:51 Fabrice Gautier
2000-10-18 11:25 Fabrice Gautier
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=20001019123121.Q474@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=Fabrice_Gautier@sdesigns.com \
--cc=ecos-discuss@sourceware.cygnus.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).