Summary: | Tethereal 0.10.0a segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alberto Garcia Hierro (Skyhusker) <tcpdevil> |
Component: | Current packages | Assignee: | PPC Porters <ppc> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 45399 | ||
Bug Blocks: |
Description
Alberto Garcia Hierro (Skyhusker)
2004-01-22 08:26:10 UTC
Does 0.9.16 do the same thing? americana root # tethereal -v tethereal 0.9.16 Compiled with GLib 2.2.3, with libpcap 0.8, with libz 1.2.1, without UCD-SNMP or Net-SNMP, without ADNS Running with libpcap version 0.8 on Linux 2.6.1-benh1 americana root # tethereal Segmentation fault As this bug wasn't going anywhere I've posted the information here on the ethereal-dev mailing list in case someone there might be able to help. Looking at Guy Harris's reply to my question on ethereal-dev he wants a strack trace rather than a system trace. Can you do this? http://www.ethereal.com/lists/ethereal-dev/200401/msg00848.html - run the app from gdb and paste the stack trace (backtrace) gdb [app] press r and then bt - alternatively enable core dumping and make gdb read it ulimit -c unlimited [app] gdb [app] corefile bt Could you try the ebuild over in bug 40660 and see if that cures the problem? It may do or may not. I have the same problem of segfault. I've tried to rebuild ethereal to get debug informations using : CFLAGS="-O2 -pipe -mcpu=7400 -maltivec -mabi=altivec -g" FEATURES="noclean nostrip" emerge ethereal but I wasn't able to complete the build, getting an "Internal compiler error"... Removing -mabi=altivec : CFLAGS="-O2 -pipe -mcpu=7400 -maltivec -g" FEATURES="noclean nostrip" emerge ethereal The build succeeded and tethereal does not segfault anymore. Rebuilding without debug : CFLAGS="-O2 -pipe -mcpu=7400 -maltivec" emerge ethereal gives a perfectly working tethereal I've already encountered exactly the same problems (1. -mabi=altivec and -g incompatibility, 2. removing -mabi=altivec solves the problem) as I have reported in bug #36127. It looks like a general problem in gcc with Altivec extensions for ABI... Should I fill a new bug for this ? Concerning ethereal doing "filter-flags -mabi-altivec" should solve the problem. Works flawlessly with gcc 3.3.3. Seems a gcc problem instead of an ethereal problem. reopened, gcc-3.3.3 isn't yet stable enough to be put even on ~ppc gcc-3.3.3_pre20040408 is now stable, I think we can close this bug. Closing |