Re: symbol lookup in ddb - bad heuristic

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Sat, Dec 10, 2022 at 01:03:06 +0300, Valery Ushakov wrote:

> That causes breakpoints on a function entry to be misreported:

Actually it's more than that.  The corresponding MD change in i386
db_frame_info that applies the same heuristic causes another side
effect.

With the heuristic I get the following backtrace from the breakpoint
at clockintr for the real problem I've been debugging (see my earlier
mail):

  db{0}> bt
  sysbeepdetach(c2f50680,c1930d9c,0,0,0,0,0,0,0,0) at netbsd:clockintr
  --- switch to interrupt stack ---

but with the MD part of the heuristic also disabled (I missed it
originally), I get:

  db{0}> bt
  clockintr(0,0,0,0,0,0,0,0,c2d72000,c010322a) at netbsd:clockintr
  intr_kdtrace_wrapper(c2f50680,c1930d9c,0,0,0,0,0,0,0,0) at netbsd:intr_kdtrace_wrapper+0x21
  --- switch to interrupt stack ---

Yes, I should have realized I did see that intr_kdtrace_wrapper in
another backtrace, taken earlier, further down the call chain:

  db{0}> bt
  hardclock(0,0,da3eef6c,c04ac8f1,0,0,0,0,0,0) at netbsd:hardclock+0x23
  clockintr(0,0,0,0,0,0,0,0,c2d72000,c010322a) at netbsd:clockintr+0x2a
  intr_kdtrace_wrapper(c2f50680,c1930d9c,0,0,0,0,0,0,0,0) at netbsd:intr_kdtrace_wrapper+0x21
  --- switch to interrupt stack ---

but it kinda drifted out of focus...

-uwe