Re: Gdb on ia64

[Andreas Schwab <schwab@suse.de>]

Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz> writes:

|> 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).

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."