home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!rpi!uwm.edu!ogicse!henson!news.u.washington.edu!serval!phys1.physics.wsu.edu!hlu
- From: hlu@phys1.physics.wsu.edu (Hongjiu Lu)
- Newsgroups: comp.os.linux
- Subject: Re: Shared Libraries Considered Harmful
- Message-ID: <1992Aug13.205728.25720@serval.net.wsu.edu>
- Date: 13 Aug 92 20:57:28 GMT
- Article-I.D.: serval.1992Aug13.205728.25720
- References: <1992Aug12.164218.13155@crd.ge.com> <1992Aug12.182534.12667@unislc.uucp> <1992Aug12.202438.19963@serval.net.wsu.edu> <1992Aug13.124928.13672@crd.ge.com>
- Sender: news@serval.net.wsu.edu (USENET News System)
- Organization: Washington State University
- Lines: 21
-
- I am not sure if you can run gdb on binaries linked with the shared libs.
- Since gcc 2.2.2, if you compile foo with -g, libg.a will be used instead
- of libc.a.
-
- --
- H.J.
- Gcc/libc maintainer for Linux.
- In article <1992Aug13.124928.13672@crd.ge.com>, davidsen@ariel.crd.GE.COM (william E Davidsen) writes:
- |> In article <1992Aug12.202438.19963@serval.net.wsu.edu>, hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:
- |> | I am not sure about that. With jump table, we just added one jump for
- |> | each function. If the libs are compiled with -O -fomit-frame-pointer,
- |> | I don't think you will notice a thing.
- |>
- |> Of course the debugger doesn't work if you compile the libraries with
- |> no frame pointer, and if you get a dump from a procedure called with bad
- |> parameters you may not be able to find out what happened. I wouldn't do
- |> that personally, but then I wouldn't upgrade my C compiler and library
- |> unless there was a good reason, either.
- |> --
- |> bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
- |> I admit that when I was in school I wrote COBOL. But I didn't compile.
-