From: Kevin Buettner <kevinb@redhat.com>
To: Iztok Kobal <iztok.kobal@sysen.si>
Cc: gdb@sources.redhat.com
Subject: Re: Problem debugging SOs
Date: Tue, 27 Aug 2002 08:04:00 -0000 [thread overview]
Message-ID: <1020827150400.ZM3420@localhost.localdomain> (raw)
In-Reply-To: Iztok Kobal <iztok.kobal@sysen.si> "Re: Problem debugging SOs" (Aug 27, 7:40am)
On Aug 27, 7:40am, Iztok Kobal wrote:
> code to be debugged was compiled with the gcc-2.95.2 -g3
>
> No more problems seem to be directly related to the SO debugging
> New problem with gdb-5.2.1 is that the <Step Into> (gdb step) behaves as
> if it was the <Step Over) (gdb next) even in the simplest (statically
> linked single .c) projects.
Are you certain that the files containing the functions that you're
trying to step into were compiled with -g ? The only time I see the
behavior you describe is when I've forgotten to use -g.
Kevin
next prev parent reply other threads:[~2002-08-27 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 2:43 Iztok
2002-08-23 7:53 ` Kevin Buettner
2002-08-26 2:43 ` Iztok Kobal
2002-08-26 8:43 ` Kevin Buettner
2002-08-26 22:41 ` Iztok Kobal
2002-08-27 8:04 ` Kevin Buettner [this message]
2002-08-27 22:17 ` Iztok Kobal
2002-08-27 22:57 ` Kevin Buettner
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=1020827150400.ZM3420@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=iztok.kobal@sysen.si \
/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