On Tue, Jan 18, 2000 at 04:36:43AM +0200, Iani Brankov wrote:
> Daniel Eischen wrote:
> >
> > > Hi,
> > >
> > > after making world of a CURRENT cvsupped yesterday, one of my
> > > applications stopped working because of a Segmentation fault.
> > >
> > > The C procedure where the problem pops has about 64k local variables.
> > > here's the assembly output of the procedure's beginning:
> > >
> > > 0x805bb60 <transaction_read_objects>: pushl %ebp
> > > 0x805bb61 <transaction_read_objects+1>: movl %esp,%ebp
> > > 0x805bb63 <transaction_read_objects+3>: subl $0x1000c,%esp
> > > 0x805bb69 <transaction_read_objects+9>: pushl %edi
> > >
> > >
> > > The Segmentation fault happens when the process tries to push %edi in
> > > the stack, which has been just decreased by 0x1000c.
> >
> > Are you using threads?
> >
>
> Yes, it does.
> Do all the threads in a process use the same stack segment in some
> way?
Thread stacks have a default size of 64kB. libc_r now uses growable stacks
with "guard pages" between stacks to try to catch stack overflow. It looks
like it did you some good. =)
You will need to specify an alternate stack during thread creation to get
around this size limit, or you can just use less stack space.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
