Red Hat Bugzilla – Bug 249343
w3m crashes immediately
Last modified: 2007-11-30 17:12:11 EST
w3m crashes on x86_64 immediately with segfault. I don't know whether it crashes
on other architectures as well.
The crash is in gc library so I'm cc-ing gc library maintainer.
0x00002aaaaaaf2ec9 in GC_malloc (bytes=24) at thread_local_alloc.c:176
176 GC_FAST_MALLOC_GRANS(result, granules, tiny_fl, DIRECT_GRANULES,
#0 0x00002aaaaaaf2ec9 in GC_malloc (bytes=24) at thread_local_alloc.c:176
#1 0x000000000045ccbe in newGeneralList () at textlist.c:23
#2 0x000000000040fcd3 in main (argc=1, argv=0x7fff0ced58b8,
envp=<value optimized out>) at main.c:408
#3 0x0000003b51a1daa4 in __libc_start_main () from /lib64/libc.so.6
#4 0x00000000004045d9 in _start ()
Reproduced with current packages in development.
(Doesn't happen with f7 x86_64 for me.)
Could you try reverting to gc-6.8 to see if that makes a difference?
Yes, reverting gc to 6.8 helps. And rebuilding w3m against gc-7.0 helps too. So
that means ABI break in gc. So all dependencies of gc should be rebuilt.
[root@rawhide64 ~]# repoquery --whatrequires 'libgc.so.1()(64bit)'
Ccing owners of the above packages.
I would prefer if gc were held back to 6.8, since it's only in updates-testing.
This is a gc bug after all, it's not meant to break ABI. Looking at the gc
mailing list, there seems to be a number of issues with 7.0, i.e. ABI could
break again with further 7.x updates.
(In reply to comment #4)
> I would prefer if gc were held back to 6.8, since it's only in updates-testing.
> This is a gc bug after all, it's not meant to break ABI. Looking at the gc
> mailing list, there seems to be a number of issues with 7.0, i.e. ABI could
> break again with further 7.x updates.
For Fedora 7 that's clear - there should be no ABI breaking update. But for
Fedora 8 I'd leave that on the gc maintainer. Rex?
on Tomas Mraz request, I already started w3m build on koji for devel branch.
w3m-0.5.2-2 built successfully against gc-7.0
Reopening for F-7. I submitted a patch to work around this for bug 248700.
will wait for new release of gc for F7 and then accordingly release new version
of w3m for F7 only.
I think that for F7 the gc should be fixed which is the bug 248700.
So no need for reopening this one.
(IMHO gc should be fixed for F8 - rawhide too.)