All my amd64 problems appear to be KSE
eischen at vigrid.com
Sat Jun 5 12:21:49 PDT 2004
On Sat, 5 Jun 2004, Sean McNeil wrote:
> On Sat, 2004-06-05 at 09:57, Daniel Eischen wrote:
> > On Sat, 5 Jun 2004, Sean McNeil wrote:
> > > With regards to gnome-specific or if KDE has the same issue, I cannot
> > > answer. I do not use KDE. It would appear to be gnome-specific
> > > (gtk-specific?). Emacs has never given me any problems, but neither has
> > That includes glib also, right?
> > > nautilus, the panel, or a number of other gnome applications.
> > >
> > > For the moment, I highly suspect this is a pthread/readline interaction
> > > causing the crashes.
> > Why do you suspect that?
> I suspect libreadline because the only time I get a crash is when I type
> in a character to an application or when it is starting up (resize?).
> Sorry, it just occurred to me that this might be useful information.
> Looking at my bash problem, I can see there is an issue with any program
> that might get a signal and then want to call an older installed handler
> What happens is that sigaction is called and returns a context with the
> _thr_sig_handler function. So the new signal handler is called and then
> it in turn wants to call the old one. But the old handler isn't called
> as a sigaction.
> I suppose it is really libreadline at fault here and it should check
> SA_SIGINFO. Do you think there might be others that don't check either?
I don't know; perhaps.
> Why doesn't this show an issue in i386? Is it just luck that info has
> been null and not caused a bad dereference?
When I write signal handlers, I usually check info and ucp to
make sure they are not null before using them. Actually, I
rarely use them anyways so it doesn't matter if they are null
More information about the freebsd-threads