segmentation violation with large symbol tables

Thread View: gnu.gdb.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Glenn Engel Wed, 15 Mar 1989 15:23

#715

Author: Glenn Engel
Date: Wed, 15 Mar 1989 15:23

17 lines
1256 bytes

I received a segmentation violation when attempting to read a file
which had a 2.1 Mbyte symbol table.  A backtrace revealed the culprit
to be the alloca() call near line 1500 of dbxread.c in
symbol_file_command().  I'm not sure whether this is a gdb problem or
a kernel bug.  What seems to be happening is the kernel is generating
a segmentation violation when the stack is extended in alloca.
Evidently it assumes a 2.1 Mbyte stack extension all at once really
means the program is out-to-lunch.  Another possibility is that there
is a kernel parameter that needs to be tuned for this type of
application.  At any rate, changing the alloca to malloc fixes my
problem but also requires a free at the end of the function.

--
 |  Glenn R. Engel
 |  Hewlett-Packard 
 |  (206) 335-2066
 |  glenne%hplsla@hplabs.hp.com

Re: segmentation violation with large symbol tables

#717

Author: Anton Rang
Date: Wed, 15 Mar 1989 17:20

8 lines
1085 bytes

Is your stack limit set too low?  Maybe try 'limit stack 3m' or
something like that, if you're using the shell.  On the other hand,
should there be some "reasonable" maximum size for stack allocation?

+---------------------------+------------------------+----------------------+
| Anton Rang (grad student) | "VMS Forever!"         | "Do worry...be SAD!" |
| Michigan State University | rang@cpswh.cps.msu.edu |                      |
+---------------------------+------------------------+----------------------+

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads