Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Satyavathi Malladi <satya@ittc.ku.edu>
To: <gdb@sources.redhat.com>
Subject: Breakpoints
Date: Mon, 16 Dec 2002 19:57:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0212162156450.18497-100000@basie.ittc.ku.edu> (raw)


Hi,
  I have compiled a program using the gcc compiler with the options -g and
-ax (-ax is the  option to enable block profiling). I am debugging the
program using gdb-5.2 . I set a breakpoint at main. When the program hits
the breakpoint, I obtained the backtrace of the program.It was as follows:
(gdb) bt
#0  main () at ex7.c:7
#1  0x400a5316 in __libc_start_main (main=0x8048a34 <main>, argc=1,
ubp_av=0xbffff594, init=0x80487ac <_init>, fini=0x804a1d0 <_fini>,
rtld_fini=0x4000d2fc <_dl_fini>, stack_end=0xbffff58c)
at ../sysdeps/generic/libc-start.c:129

Then I continued the program using the command "continue". Then the
breakpoint at main was hit again.

Program received signal SIGTRAP, Trace/breakpoint trap.
0x08048a50 in main () at ex7.c:7
Then when I tried to obtain the backtrace, I got the following output:
(gdb) bt
#0  0x08048a50 in main () at ex7.c:7
#1  0xbffff568 in ?? ()

Can someone help me figure out why this is happening.

Thanks,
Satya


             reply	other threads:[~2002-12-17  3:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 19:57 Satyavathi Malladi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27  3:10 gdb_indent vs. dwarf2read Daniel Jacobowitz
2003-01-27 17:30 ` Andrew Cagney
2003-01-27 17:43   ` Daniel Jacobowitz
2003-01-27 20:02     ` breakpoints jacques
     [not found] <01BF4C88.F6D54B20.davidwilliams@ozemail.com.au>
     [not found] ` <991222035342.ZM17881@ocotillo.lan>
1999-12-22  7:09   ` Breakpoints Mark Salter
1999-12-22 15:49 ` Breakpoints J.T. Conklin
1999-12-22 13:06 Breakpoints David Williams

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=Pine.LNX.4.33.0212162156450.18497-100000@basie.ittc.ku.edu \
    --to=satya@ittc.ku.edu \
    --cc=gdb@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