Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: [PATCH] i386 vsyscall DSO implementation | Date | 25 Apr 2003 14:00:53 -0700 |
| |
Followup to: <16041.24730.267207.671647@napali.hpl.hp.com> By author: David Mosberger <davidm@napali.hpl.hp.com> In newsgroup: linux.dev.kernel > > I like this. Even better would be if all platforms could do the same. > I'm definitely interested in doing something similar for ia64 (the > getunwind() syscall was always just a stop-gap solution). > > I assume that these kernel ELF images would then show up in > dl_iterate_phdr()? > > To complete the picture, it would be nice if the kernel ELF images > were mappable files (either in /sysfs or /proc) and would show up in > /proc/PID/maps. That way, a distributed application such as a remote > debugger could gain access to the kernel unwind tables on a remote > machine (assuming you have a remote filesystem). >
How about /boot?
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |