ee150a3376
Normally, we can get away with just reading the 1k buffer for the string, since the placement of the data is generally no where near the end of the file. However, it's possible that the string is within the last 1k of the file, in which case the read will fail, and we'll not produce the proper records needed for devmatch to work. By reading using EF_SEG_READ_STRING, we automatically work around these problems while still retaining safety. This fix a problem with devmatch where we wouldn't load certain modules (like ums). This didn't always happen (my tree didn't exhibit it, while nathan's did because his optimization options were more agressive). Reported by: nathanw@ |
||
|---|---|---|
| .. | ||
| ef_aarch64.c | ||
| ef_amd64.c | ||
| ef_i386.c | ||
| ef_nop.c | ||
| ef_obj.c | ||
| ef_powerpc.c | ||
| ef_sparc64.c | ||
| ef.c | ||
| ef.h | ||
| fileformat | ||
| kldxref.8 | ||
| kldxref.c | ||
| Makefile | ||
| Makefile.depend | ||