> | 1 .reg/23268 0000004c 00000000 00000000 00002554 2**2 > | CONTENTS > | 2 .reg 0000004c 00000000 00000000 00002554 2**2 > | CONTENTS
This offset (0x2554) might be right for that file, or maybe 4 off. I haven't triple-checked the calculations. > | 3 .reg2/23268 00000000 00000000 00000000 00000000 2**2 > | CONTENTS > | 4 .reg2 00000000 00000000 00000000 00000000 2**2 > | CONTENTS This is clearly wrong, it being zero. This suggests to me that elfcore_grok_lwpstatus still does not have HAVE_LWPSTATUS_T_PR_FPREG. Can you check that again? I noticed some problems with the layout crash was writing. These do not explain why gdb can't grok it, I don't think. The layout it was writing is correct enough to be read clearly, I believe. However, it was wrong it a couple of nits and I changed crash (exec/elfcore.c) in cvs to correct that. Like I say, I don't think this fixes the gdb issue. But it does perturb all the offsets and such. So please build a fresh crash server and try the new output instead. It may still have issues, but we can take it from there. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
