Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
To: Andreas Schwab <schwab@suse.de>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb@sources.redhat.com
Subject: Re: Gdb on ia64
Date: Thu, 19 Jun 2003 19:31:00 -0000	[thread overview]
Message-ID: <20030619193111.GA18680@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <jeznkdrhru.fsf@sykes.suse.de>

Hello,

> |> > > > Could you tell us the address which is giving gdb problems along with
> |> > > > a disassembly of code near that address?  (Basically, I need to see
> |> > > > the three instructions in the bundle.)
> |> > > 
> |> > > Address: 20000000003b4c18
> |> > > No function contains this address and the memory is not accessible.
> |> > 
> |> > Do you know why GDB was trying to put a breakpoint there?
> |> 
> |> I have no clue -- I did not ask for one and I don't know anything about gdb
> |> internals so I don't know why it tries to put there one on its own.
> 
> Perhaps it's the shlib events breakpoint (use "maintenance info
> breakpoints" to list internal breakpoints).

yes,

Num Type           Disp Enb Address            What
-1  shlib events   keep y   0x20000000003b4c18

Zdenek


      reply	other threads:[~2003-06-19 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 11:04 Zdenek Dvorak
2003-06-13 15:34 ` Kevin Buettner
2003-06-13 18:06   ` Zdenek Dvorak
2003-06-13 18:43     ` Kevin Buettner
2003-06-14 12:35       ` Zdenek Dvorak
2003-06-14 14:00         ` H. J. Lu
2003-06-18  0:19         ` Kevin Buettner
2003-06-18  0:36           ` Zdenek Dvorak
2003-06-19  0:13             ` Kevin Buettner
2003-06-19 14:53               ` J. Johnston
2003-06-19 19:28             ` Andreas Schwab
2003-06-19 19:31               ` Zdenek Dvorak [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=20030619193111.GA18680@atrey.karlin.mff.cuni.cz \
    --to=rakdver@atrey.karlin.mff.cuni.cz \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --cc=schwab@suse.de \
    /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