Date: Fri, 18 Sep 1998 08:28:00 -0700 From: David Greenman <dg@root.com> To: Robert Withrow <bwithrow@BayNetworks.COM> Cc: hackers@FreeBSD.ORG Subject: Re: GDB modifies shared libraries? Message-ID: <199809181528.IAA21509@implode.root.com>
next in thread | raw e-mail | index | archive | help
>I was debugging a (large) program using GDB on an xterm (which >prevented me from getting the exact text, as you will see). This >is on 2.2.6-RELEASE on a P6-200 with 128M ram. I was running as >a normal user, not root. > >I issued the "run" command and GDB said that /usr/lib/libc.so.3.1 >had changed and it was re-loading it. That was followed immediately >by X freezing, and then a spontaneous re-boot. > >After the system re-booted, sure enough the date on /usr/lib/libc.so.3.1 >had been changed! > >Now, with this program, GDB generally says that the *program* has changed >*every* time I issue the "run" command, but I thought that was just a >GDB problem. But I don't understand how GDB can override protections >on /usr/lib/libc.so.3.1 in order to change its date. This seems like >an OS bug. > >Any fixes around? I think this may have been fixed already in newer versions of FreeBSD. I seem to recall a procfs bug (or was it ptrace??) that was responsible. Is there any chance you code try the same thing on a 2.2.7 (or -current) machine? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809181528.IAA21509>