problem debugging assembler functions

[Daniel Jacobowitz]

On Tue, Jun 14, 2005 at 07:19:21PM +0400, Vladimir Prus wrote:
> Do you mean prologue analysis for assembler modules? For C++ modules DWARF2 
> info contains everything. 
> 
> Well, I don't need to analyse prologue for assembler modules at all, because
> if I understand correctly it's only needed to proper unwind stack, and I have 
> a much better way for stack unwinding. My target is actually a simulator, so 
> I just store register values on each call instruction and can fetch them via
> extended version of "get registers" remote protocol command.

It was an example of something which will go wrong without any symbols;
this is an assumption in GDB.  I bet you'll encounter it again
elsewhere.

> So, moving 'find_pc_line' above will reasult in extra lookup only if 
> - the command is stepi/nexti, or
> - the first condition evaluates to true (which means we've entered   
>   undebuggable code)
> 
> I have no idea is that's bad or not performance-wise, just clarifying what's
> going on.

Hmm, that's encouraging!  This might be a good improvement, then.

> > It does seem plausible, but it would 
> > need wider testing.
> 
> Ok.

-- 
Daniel Jacobowitz
CodeSourcery, LLC