public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Narayanan, Anita (CTS)" <Nanita@chn.cognizant.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] sprintf problem
Date: Tue, 09 Jan 2001 10:17:00 -0000	[thread overview]
Message-ID: <3A5B55A3.30068A4C@redhat.com> (raw)
In-Reply-To: <8F1D166D08ACD41196EE00B0D020944B73EAB3@CTSINENTSXUB>

"Narayanan, Anita (CTS)" wrote:
> But the code gives a segmentation violation error at the sprintf() function
> whenever i try to copy a variable value into some buffer.
> for eg.
> sprintf(buf,"%d TYPE", m_type);
> 
> Has anybody encountered such a problem with sprintf() function with i386 as
> the target machine? If so, can you kindly help us to resolve the issue?

I haven't. What happens if you run the eCos tests sprintf1 and sprintf2?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

      reply	other threads:[~2001-01-09 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 22:40 Narayanan, Anita (CTS)
2001-01-09 10:17 ` Jonathan Larmour [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=3A5B55A3.30068A4C@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=Nanita@chn.cognizant.com \
    --cc=ecos-discuss@sources.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).