From: Jitendra Pawar <jitendrap@ryussi.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: The step-Over (next) command seems repetitively displaying same statement execution
Date: Wed, 23 Dec 2015 03:23:00 -0000 [thread overview]
Message-ID: <CAO9sCwTnTUiSxpA3Qvtp7G3oXGi=WsNj8DCr=Cccj6reOPFLtg@mail.gmail.com> (raw)
In-Reply-To: <83bn9iqwrt.fsf@gnu.org>
Hello Eli,
I am sorry, I forgot to mention that.
Compilation command is: " gcc hello.c -g " thats it.
gcc version is: 4.6.3
gdb version is: GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Thanks,
- Jitendra Pawar
On Tue, Dec 22, 2015 at 9:51 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 22 Dec 2015 17:33:16 +0530
>> From: Jitendra Pawar <jitendrap@ryussi.com>
>>
>> $ gdb -q a.out
>> Reading symbols from /home/jitendra/work/roughwork/a.out...done.
>> (gdb) br main
>> Breakpoint 1 at 0x40054c: file hello.c, line 9.
>> (gdb) run
>> Starting program: /home/itendrap/work/roughwork/a.out
>> warning: no loadable sections found in added symbol-file
>> system-supplied DSO at 0x7ffff7ffa000
>>
>> Breakpoint 1, main () at t.c:9
>> 9 c = (char*) malloc (12);
>> (gdb) n
>> 9 c = (char*) malloc (12);
>> (gdb) n
>> 11 memcpy(c, "Hello World", 12);
>> (gdb) n
>> 13 printf("%s\n", c);
>> (gdb) n
>> Hello World
>> 14 }
>> (gdb)
>> ------------------------------------------------------------------------
>>
>> Can anyone please explain whats going wrong here? Why the malloc
>> statement 'c = (char*) malloc (12);' gets repeated?
>
> What compilation command and switches did you use to compile this
> program?
prev parent reply other threads:[~2015-12-23 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 12:03 Jitendra Pawar
2015-12-22 16:21 ` Eli Zaretskii
2015-12-23 3:23 ` Jitendra Pawar [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='CAO9sCwTnTUiSxpA3Qvtp7G3oXGi=WsNj8DCr=Cccj6reOPFLtg@mail.gmail.com' \
--to=jitendrap@ryussi.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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