aboutsummaryrefslogtreecommitdiff
path: root/gdb/frame-unwind.c
diff options
context:
space:
mode:
authorAlan Modra <amodra@gmail.com>2023-08-27 21:17:05 +0930
committerAlan Modra <amodra@gmail.com>2023-08-27 21:21:38 +0930
commit6785fd72d503fd13bfec31a2897694f1590031eb (patch)
treefe86bf1be8d09d2ebe79083349fcdb67db04eb5d /gdb/frame-unwind.c
parent8606b47e94078e77a53f3cd714272c853d2add22 (diff)
downloadgdb-6785fd72d503fd13bfec31a2897694f1590031eb.zip
gdb-6785fd72d503fd13bfec31a2897694f1590031eb.tar.gz
gdb-6785fd72d503fd13bfec31a2897694f1590031eb.tar.bz2
PE dos_message
I was looking at dos_message and wondering why we have H_PUT_32 in _bfd_XXi_only_swap_filehdr_out but no H_GET_32 in pe_bfd_object_p. On a big-endian machine this would result in scrambling the code and strings constained in dos_message. Rather than fix the lack of H_GET_32 in pe_bfd_object_p, I decided it doesn't make sense to store dos_message internally as an array of ints. include/ * coff/internal.h (struct internal_extra_pe_filehdr): Make dos_message a char array. * coff/msdos.h (struct external_DOS_hdr): Flatten dos_message. * coff/pe.h (struct external_PEI_filehdr): Likewise. bfd/ * libcoff-in.h (struct pe_tdata): Make dos_message a char array. * libcoff.h: Regenerate. * peXXigen.c (_bfd_XXi_only_swap_filehdr_out): memcpy dos_message to output. * peicode.h (pe_mkobject): Don't memset already zeroed pe_opthdr. Tidy allocation of tdata.pe_obj_data. Set up dos_message from.. (default_dos_message): ..this. New static array.
Diffstat (limited to 'gdb/frame-unwind.c')
0 files changed, 0 insertions, 0 deletions