Re: debug info format
On Tue, 29 Jan 2002 14:31:03 -0500 Daniel Jacobowitz [EMAIL PROTECTED] wrote: DJ You should add swap space in that case. And: Note that /etc/security/limits.conf contains these lines: *harddata10 *hardrss 10 *hardstack 10 *hardas 10 (limiting memory use to 10 Kbs to prevent lockups). DJ after adding swap space increase the limits. I'll try. I already have 192M of swap. But on kernel 2.4.7 my system could lock up in case of heavy memory usage by g++ or ld. Now I am using 2.4.13, with new VM things might be better... But: in case of memory shortage g++ uses tmp files and in many cases can compile even very big source. It's not good that I can't say this about ld. 500 megs of free disk space could not help ld. :( Where can I find any docs on debug info formats comparison? gcc docs just say this format used in old System V systems, this format used in old BSD systems. It may be interesting for historics, but do not help in my case. DJ Stabs is the more compact of your alternatives. Thanks for this answer! Short and clear! Regards, Alexei.
Re: debug info format
On Mon, Jan 28, 2002 at 05:52:40PM +0200, Alexei Khlebnikov wrote: Hello all. I have a problem: my shared library cannot be linked, because it's too big (all objs are 140 megs in size). I compile sources with -g option. As I understand, g++ produces level 2 debug info in stubs+ format. I want to use breakpoints and see stack backtraces. Can I switch to level 1 info? (I guess: no.) What debug info format is smaller and easier (linker consumes less memory) to link? Please wrap lines at 72 chars. Why can't you link it? Just because it's big shouldn't stop anything. What platform is this? -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer
Re: debug info format
On Tue, 29 Jan 2002, Daniel Jacobowitz wrote: On Mon, Jan 28, 2002 at 05:52:40PM +0200, Alexei Khlebnikov wrote: Hello all. I have a problem: my shared library cannot be linked, because it's too big (all objs are 140 megs in size). I compile sources with -g option. As I understand, g++ produces level 2 debug info in stubs+ format. I want to use breakpoints and see stack backtraces. Can I switch to level 1 info? (I guess: no.) What debug info format is smaller and easier (linker consumes less memory) to link? Please wrap lines at 72 chars. Why can't you link it? Just because it's big shouldn't stop anything. What platform is this? I'll second this. I've linked some large files (circa 500MB) with stabs+ info without a problem. If you're bent on using stabs and not stabs+, though, you can compile the files with -gstabs. See the gcc docs before doing this, though, as there are some caveats if you're using gdb. C
