public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@iskramedical.si>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: remote debugging and source files
Date: Tue, 24 Aug 2004 17:42:00 -0000	[thread overview]
Message-ID: <412B7E21.2080500@iskramedical.si> (raw)
In-Reply-To: <412B6ABC.9060804@qnx.com>

Kris Warkentin wrote:
> auto-solib-add will only work properly if gdb successfully sets the 
> solib event breakpoint in the loader.  Try 'maint info breakpoints' and 
> see if it's being set.  You could also try setting stop-on-solib-events 
> to see if it's actually stopping.  Sometimes you have problems if there 
> is a different version of the loader on host and target.
> 

It seems that solib events have enabled breakpoint,

(gdb) maintenance info breakpoints
Num Type           Disp Enb Address    What
-2  longjmp resume keep n   0x00000000
-3  shlib events   keep y   0x4000b8d8

but execution won't stop if I do
	set stop-on-solib-events 1


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]

  reply	other threads:[~2004-08-24 17:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:05 Hinko Kocevar
2004-08-24 15:34 ` Hinko Kocevar
2004-08-24 15:56   ` Hinko Kocevar
2004-08-24 16:35     ` Kris Warkentin
2004-08-24 17:42       ` Hinko Kocevar [this message]
2004-08-24 17:53         ` Daniel Jacobowitz
2004-08-24 18:05         ` Kris Warkentin
2004-08-25 13:58           ` Hinko Kocevar
2004-08-25 14:16             ` Daniel Jacobowitz
2004-08-25 14:30               ` Hinko Kocevar
2004-08-26 19:38                 ` remote debugging and source files - SOLVED Hinko Kocevar
2004-08-25 14:33             ` remote debugging and source files Kris Warkentin

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=412B7E21.2080500@iskramedical.si \
    --to=hinko.kocevar@iskramedical.si \
    --cc=gdb@sources.redhat.com \
    --cc=kewarken@qnx.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).