public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: iainmelvin <iainmelvin@gmail.com> To: kseitz@sources.redhat.com Cc: insight-prs@sources.redhat.com, Subject: Re: insight/235: "Step" and "Next" doesn't work. Instead I get "Step Asm Inst" and "Next Asm Inst" Date: Fri, 16 Sep 2005 18:43:00 -0000 [thread overview] Message-ID: <20050916184301.24518.qmail@sourceware.org> (raw) The following reply was made to PR insight/235; it has been noted by GNATS. From: iainmelvin <iainmelvin@gmail.com> To: insight-gnats@sources.redhat.com Cc: Subject: Re: insight/235: "Step" and "Next" doesn't work. Instead I get "Step Asm Inst" and "Next Asm Inst" Date: Fri, 16 Sep 2005 19:33:56 +0100 i had almost exactly these symptoms, and the problem was fixed for me by typing... (gdb) set solib-absolute-prefix / ... into the command line window in insight. The apparent 'step' and 'next' inactivity is due to gdb not being able to set breakpoints for the step/next behaviours. Not being able to get paths to libraries seems to affect gdb's ablity to set breakpoints. The solib-adbsolute-prefix variable is set at configure time for both gdb and insight, and the defaults i have in my debian [sarge 3.1] are.. gdb [gdb 6.3-debian] has the default : "" insight [GNU gdb 2004-08-11-cvs] has the default : "/usr/share". when I set the value to "/usr/share" in gdb, it has exactly the same broken behaviour with 'next' and 'step'. I guess this is down to the distribution to get the config right, so I've sent this to bugs at debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=306276 nice debugger though :)
next reply other threads:[~2005-09-16 18:43 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-09-16 18:43 iainmelvin [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-08-20 14:55 kseitz 2003-08-05 16:43 pal.frenger
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=20050916184301.24518.qmail@sourceware.org \ --to=iainmelvin@gmail.com \ --cc=insight-prs@sources.redhat.com \ --cc=kseitz@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: linkBe 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).