public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@iskramedical.si>
To: gdb@sources.redhat.com
Subject: Re: ptrace: bogus breakpoint trap
Date: Fri, 27 Aug 2004 16:27:00 -0000	[thread overview]
Message-ID: <412F6101.40207@iskramedical.si> (raw)
In-Reply-To: <412DBCA2.4030303@iskramedical.si>

Hinko Kocevar wrote:
> Hi,
> 
> While trying to solve my previous problem with dynamic shared libraries 
> and automated symbol loading I stumbled accross another problem.
> 

I got this issue sorted out - partly - by using latest gdb - 6.2.
But as the problems just won't go away there is another issue!!

Now dynamic lib symbols load fine and execution stops at set breakpoint.

Proceeding after BP that I can only use 'step' cmd to continue. If issue 
'next' once it continues to the next line of source, but if I use 'next' 
twice or more execution is stopped and pc holds location in .plt 
section. On further attempts to proceed with 'next or 'step' gdb gives 
'Cannot find bounds of current function'.

Looking at the remote protocol log for 'next' and 'step' they start to 
differ after reading contents of accessed location in .plt section. 
After that for 'step' gdb issues read general registers packet while for 
'next' gdb reads some memory location where it gets address of the 
(only) breakpoint set - after that it stops.

Any comments ?

regards,
h
-- 
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"Aì rén"	|	[Analects XII:22]

      parent reply	other threads:[~2004-08-27 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 10:34 Hinko Kocevar
2004-08-26 13:35 ` Daniel Jacobowitz
2004-08-26 15:58   ` Hinko Kocevar
2004-08-26 16:14     ` Hinko Kocevar
2004-08-27 16:27 ` Hinko Kocevar [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=412F6101.40207@iskramedical.si \
    --to=hinko.kocevar@iskramedical.si \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).