From: Kevin Buettner <kevinb@redhat.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: gdb@sources.redhat.com
Subject: Re: Gdb on ia64
Date: Wed, 18 Jun 2003 00:19:00 -0000 [thread overview]
Message-ID: <1030618001856.ZM676@localhost.localdomain> (raw)
In-Reply-To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz> "Re: Gdb on ia64" (Jun 14, 2:34pm)
On Jun 14, 2:34pm, Zdenek Dvorak wrote:
> > > > > when I try to run a program in gdb on ia64, it claims that
> > > > >
> > > > > "Can't insert breakpoint for slot numbers greater than 2."
> > > > >
> > > > > What should I do?
> > > >
> > > > Provide us with more details.
> > >
> > > all right, I just hoped it is some well known issue.
> > > I tried to use gdb on 4 processor Itanium 2 machine.
> > > When trying to run any program from it, it responds with
> > > the above message. I have tried gdb 5.2.1 and current
> > > cvs version, both behave the same way.
> >
> > 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?
BTW, the fact that the address ends in 8 is the reason for the
"Can't insert breakpoint..." message. It should end in either
0, 1, or 2.
Kevin
next prev parent reply other threads:[~2003-06-18 0:19 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 [this message]
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
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=1030618001856.ZM676@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=rakdver@atrey.karlin.mff.cuni.cz \
/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