Re: debug info format

2002-01-30 Thread Alexei Khlebnikov
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 >> *

Re: debug info format

2002-01-29 Thread Daniel Jacobowitz
reakpoints and see stack backtraces. Can I switch > >> > to level 1 info? (I guess: no.) > > I guessed right? (I've read 'man gcc', but not sure about my english.) > > >> > > >> > What debug info format is smaller and easier (link

Re: debug info format

2002-01-29 Thread Alexei Khlebnikov
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.) I guessed right? (I&

Re: debug info format

2002-01-29 Thread Christopher C. Chimelis
pile 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 smal

Re: debug info format

2002-01-29 Thread Daniel Jacobowitz
es 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'

debug info format

2002-01-29 Thread Alexei Khlebnikov
Can I switch to level 1 info? (I guess: no.) What debug info format is smaller and easier (linker consumes less memory) to link? Regards, Alexei. --