[developer] cxgbetool dumps core, hard to debug

[Dan McDonald <danmcd@mnx.io>]

So I have this dump:

> $C
08047b28 dump_block_regs+0x78(815e300, 0, 2d, feec2c90, fef5e000, 0)
08047b68 dump_regs_table+0x5d(3, 8047c84, 3, 0, 80bc2e0, 1a)
08047b98 dump_regs_t6+0x23(3, 8047c84, 3, 0)
08047bc8 get_regdump+0x73(3, 8047c84, 3, 8237e80)
08047be8 run_cmd+0xad(3, 8047c84, 8237e80, fef5e000, 8047c84, 80bc000)
08047c18 main+0x40(8047c1c, fef67784, 8047c58, 8053f0b)
08047c58 _start_crt+0x9a(3, 8047c84, fefcec77, 0, 0, 0)
08047c78 _start+0x1a(3, 8047d98, 8047da2, 8047da9, 0, 8047db1)
> ::status
debugging core file of cxgbetool (32-bit) from a05
file: /usr/sbin/cxgbetool
initial argv: cxgbetool cxgbe1 regdump
threading model: native threads
status: process terminated by SIGSEGV (Segmentation Fault), addr=1e000

And the 1e000 is in the memory specified by 815e300:

> 815e300/10P
cxgbetool`t6_sge_regs:
cxgbetool`t6_sge_regs:          0x809247d          0x1e000            
                0                  0x80ab07d          0xf                
                0x11               0x80aa9d0          0xe                
                1                  0x80aa978          



This utility has duplicate function names that make it mildly annoying.

It looks like dump_block_regs() is getting a NULL `regs` array.  The hardware in question is a T62100-LP-CR , FWIW.

Does anyone with more cxgbe experience have any insight?

I'll probably file a bug, but in case anyone looks at anything above and goes "oooh I know that," I'd appreciate knowing.  The illumos version (from SmartOS) is earlier this month.

Thanks,
Dan
------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tec45bd4a8ce9b0fc-M7db664ab8780bbee86f1de32
Delivery options: https://illumos.topicbox.com/groups/developer/subscription