Tim_Buxton@UM.CC.UMICH.EDU (10/14/90)
Speaking of debugging by having core dump, then performing post-mortem with dbx: It would simplify things immensely if the core dump procedure itself would tell you what routine execution barfed in, no? dbx knows. It should be brought in automatically to inform us. In many cases, that information alone would be a great help. Is there a way now to have the core dump tell the subprogram last called? If not, is there a simple hack to invoke dbx and pipe the output to the screen (the result of the "where" command perhaps?) If the answer to the above is no, would SGI consider an enhancement? Thanks. -Tim Buxton -OptiMetrics, Inc.