HELP: Call to signal() trashes my stack!

HELP: Call to signal() trashes my stack!

Post by Linux Newbi » Fri, 29 Oct 1999 04:00:00



>                   HELP: Call to signal() trashes my stack!


>   Reply to: Linux Newbie
>   Date: Wed, 27 Oct 1999 01:09:28 GMT
>   Organization: none
>   Newsgroups:
>          comp.os.linux.development
>   Followup to: newsgroup(s)
>I've compiled w3m on my machine, and I try to run it, but whenever I go to acce
>ss a remote page, it segfaults.  Teh core dump was useless, as the stack was tr
>ashed, so I went into gdb.  By single stepping, I discovereed that a call to si
>gnal(0 trashes the stack, so that the fucntion that called singal() goes blooey
> when it tries to return to its own caller.

>I'm using Red Hat 5.1 with a 2.0.34 kernel, and all the development tools that
>were on the CD-ROM.  I'll upgrade if it will help, but first I'd like to know w
>hat's going on.  Is this something anyone out there has heard of?  Thanks.

 
 
 

HELP: Call to signal() trashes my stack!

Post by Norm Dresne » Fri, 29 Oct 1999 04:00:00




Quote:

> >                   HELP: Call to signal() trashes my stack!
> >I've compiled w3m on my machine, and I try to run it, but whenever I go
to acce
> >ss a remote page, it segfaults.  Teh core dump was useless, as the stack
was tr
> >ashed, so I went into gdb.  By single stepping, I discovereed that a
call to si
> >gnal(0 trashes the stack, so that the fucntion that called singal() goes
blooey
> > when it tries to return to its own caller.

I've have no specific problems like that, but I'd suggest replacing the
call to signal with a call to a do-nothing routine to isolate the problem

        Norm