Seg fault

Fri Sep 15 06:56:00 GMT 2000

Andrew Haley wrote:
> mark kimsal writes:
> >
> >
> > mark kimsal wrote:
> >
> > > Tom Tromey wrote:
> > >
> > > > >>>>> "mark" == mark kimsal <chugadie.geo@yahoo.com> writes:
> > > >
> > > > mark> Is there anyway to get more information about the seg fault?
> > > >
> > > > Yes, use the debugger.
> > > >
> > > > gdb <your-app>
> > > > run
> > > > ... seg fault
> > > > bt
> > >
> > > hmm... gdb eh? I'll try it
> > >
> > > > This will give you a stack trace. That might help. You can also poke
> > > > around and find out why the crash occurred by printing local
> > > > variables, looking at the source, etc.
> > >
> >
> > GDB didn't help very much
>> I don't understand this. What do you mean? Did gdb not tell you
> where the SEGV happened?

Well, it possibly did, but I couldn't make heads nor tails of what it said. It
said something about
/lib/libc.so.6
>> > , so i started cutting out code until it worked. I found that it
> > wasn't any amount of SDL or C coding that provided the seg fault,
> > it was a parameter sent to the linker. The -lpthreads sent to the
> > linker caused a seg fault. Now I would like to know what this flag
> > does, and if removing it will introduce any roadblocks for normal
> > development? The lpthreads flag was a standard flag for gcc from
> > the SDL library.
>> pthreads is the posix thread libarary, and you need it if you use Java
> threads.

Hmm... that is not good. Any suggestions on what to do now?