GNU bug report logs - #29062
PRINTF

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29062 in the body.
You can then email your comments to 29062 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: archit soni <architgsoni <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: PRINTF
Date: Sun, 29 Oct 2017 16:29:44 +0530

[Message part 1 (text/plain, inline)]

Respected sir,
my name Archit soni.i studying in B.E in I.T. MY friend name is Parth
prajapati .he is studying in B.Tech.he has some may bug in printf in c.We
are some situation face in printf.I have already attached image and program
also. you have to see in first printf &a address and 4th printf statement
address will be change how can be possible .if find any answer  then please
reply our mail ID below.

prajapatiparth06 <at> gmail.com
architgsoni <at> gmail.com

-- 
Agsoni

[Message part 2 (text/html, inline)]

[a.c (text/x-csrc, attachment)]

[Screenshot from 2017-10-29 16-24-57.png (image/png, attachment)]

Message #8 received at 29062 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: archit soni <architgsoni <at> gmail.com>, 29062 <at> debbugs.gnu.org,
 control <at> debbugs.gnu.org
Subject: Re: bug#29062: PRINTF
Date: Sun, 29 Oct 2017 18:46:04 -0600

tag 29062 notabug
close 29062
stop

Hello,

On 2017-10-29 04:59 AM, archit soni wrote:
> my name Archit soni.i studying in B.E in I.T. MY friend name is Parth
> prajapati .he is studying in B.Tech.he has some may bug in printf in c.We
> are some situation face in printf.I have already attached image and program
> also. you have to see in first printf &a address and 4th printf statement
> address will be change how can be possible .if find any answer  then please
> reply our mail ID below.

This is not a relevant mailing list for such questions.

This is the GNU Coreutils mailing list, which is relevant for questions 
about the printf unix command.

You are asking about the printf C-library function.

While both are named the same, and also share similar functionality,
they are quite different topics.

If you reached this mailing list after reading a manual page (e.g.
typing "man printf"), then it was likely the wrong manual page.

For the unix command, try:
   man 1 printf
For the C function, try:
   man 3 printf

Other programing resources could be the GNU LibC manual:

https://www.gnu.org/software/libc/manual/html_node/Formatted-Output-Basics.html#Formatted-Output-Basics

The POSIX printf function page:
  http://pubs.opengroup.org/onlinepubs/9699919799/functions/printf.html

Websites such as:
  http://www.cplusplus.com/reference/cstdio/printf/

Or Q&A websites such as StackOverflow.com .


While I have not tried to run your code,
from a cursory look I'd suggest using "%p" when printing pointers,
and ensuring all types are correct (that is: do not ignore any compiler
warnings about incorrect types for printf).

However, we can not provide further support about programming questions
in this mailing list.


As such, I'm closing this bug.

Regards,
 - assaf

Message #15 received at 29062 <at> debbugs.gnu.org (full text, mbox):

From: Eric Blake <eblake <at> redhat.com>
To: Assaf Gordon <assafgordon <at> gmail.com>, archit soni
 <architgsoni <at> gmail.com>, 29062 <at> debbugs.gnu.org, control <at> debbugs.gnu.org
Subject: Re: bug#29062: PRINTF
Date: Mon, 30 Oct 2017 08:56:01 +0100

[Message part 1 (text/plain, inline)]

On 10/30/2017 01:46 AM, Assaf Gordon wrote:

> 
> This is not a relevant mailing list for such questions.

One more point - attaching a screenshot of plain text is wasteful of
bandwidth; it's better to copy-and-paste relevant text content, rather
than forcing people to transcribe the screenshot.

Another observation:

> int main()	{
>     typedef struct me {
>         char str[8];
>         int a;
>         int b;
>     }m;
>     m a;
>     
> #include <string.h>

Mid-function includes like this are almost never going to work the way
you expect.  #includes should always be at the file scope.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.