This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I'd like to revisit the question of how to proceed with the s390 frame unwinding / prologue analysis code. I'd like to commit my prologue analysis changes, but the IBM GDB folks have expressed a general interest in keeping the prologue analysis logic minimal and using Dwarf CFI everywhere. So I'd like to outline my reasons, and see what the community thinks is the best approach to take.
You mean: [just for the record]: new prologue analyzer for S/390 http://sources.redhat.com/ml/gdb-patches/2003-04/msg00352.html
Note: This patch changes gdb common code in a manner that might cause problems for other platforms. Use the debugger sources created by appyling this patch only to build a debugger for the s390 or s390x architectures.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |