| Summary: | Midori crashes with Segmentation fault | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Fabian Wannenmacher <f.wanne> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | fundawang, marja11, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | midori glibc | CVE: | |
| Status comment: | |||
| Attachments: | gdb-bt | ||
|
Description
Fabian Wannenmacher
2011-09-20 02:46:27 CEST
can you attach log ? seems is related to libpng: on maageia-dev ml from funda: "Now the migration is almost done here. The left packages are: Won't build due to other reasons: eclipse, glibc, midori, R-base, xemacs [....]" Source RPM:
midori-0.3.6-3.mga2.src.rpm =>
midori there was no update of midori, so still valid I think CC:
(none) =>
fundawang Yes, it's still valid. Where can i find a log file of midori? I think there is none. (In reply to comment #4) > Yes, it's still valid. > Where can i find a log file of midori? I think there is none. enable the media core debug then urpmi midori-debug and gdb midori http://mageia.org/wiki/doku.php?id=debugging_software_crashes Created attachment 913 [details]
gdb-bt
Program received signal SIGSEGV, Segmentation fault. 0x00007ffff1f4bd80 in __sigsetjmp () from /lib64/libc.so.6 @ Fabian Is the bug still there in updated cauldron? @ tmb Can you please read the back trace and tell whether I'm correct to think glibc is the culprit? TBH, I know near to nothing about bt's CC:
(none) =>
marja11, tmb midori 0.4.2 is in the repos since 2011-11-12. Is this version still segfaulting? No, now everything works fine. Status:
NEW =>
RESOLVED |