libtext-unaccent-perl segmentation fault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libtext-unaccent-perl (Debian) |
Fix Released
|
Unknown
|
|||
libtext-unaccent-perl (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
I've got core dumps caused by libtext-
the same error is fixed already on debian:
https:/
After compiling the source package from debian here:
https:/
everything works fine.
Kind regards,
J. Barth
root@serv7:/tmp# gdb /usr/sbin/apache2 /tmp/core.
GNU gdb (Ubuntu 7.11.1-
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://
Find the GDB manual and other documentation resources online at:
<http://
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/
warning: core file may not match specified executable file.
[New LWP 18896]
[New LWP 18932]
[New LWP 18908]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
Core was generated by `/usr/sbin/apache2 -k start'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI___libc_free (mem=0x56170000
2951 malloc.c: Datei oder Verzeichnis nicht gefunden.
[Current thread is 1 (Thread 0x7f186eea6780 (LWP 18896))]
(gdb) backtrace
#0 __GI___libc_free (mem=0x56170000
#1 0x00007f185205afd8 in unac_string () from /usr/lib/
#2 0x00007f185205a28d in ?? () from /usr/lib/
#3 0x00007f186a99a20a in Perl_pp_entersub () from /usr/lib/
#4 0x00007f186a993046 in Perl_runops_
#5 0x00007f186a918276 in Perl_call_sv () from /usr/lib/
#6 0x00007f186a39ac48 in modperl_callback () from /usr/lib/
#7 0x00007f186a39b596 in modperl_
#8 0x00007f186a39bd0f in modperl_
#9 0x00007f186a3960fb in ?? () from /usr/lib/
#10 0x00007f186a396338 in modperl_
#11 0x00005617ab885140 in ap_run_handler ()
#12 0x00005617ab8856c6 in ap_invoke_handler ()
#13 0x00005617ab89cba2 in ap_process_
#14 0x00005617ab89cd50 in ap_process_request ()
#15 0x00005617ab898e1e in ?? ()
#16 0x00005617ab88f0f0 in ap_run_
#17 0x00007f186b0e77e9 in ?? () from /usr/lib/
#18 0x00007f186b0e7a74 in ?? () from /usr/lib/
#19 0x00007f186b0e88c5 in ?? () from /usr/lib/
#20 0x00005617ab86779e in ap_run_mpm ()
#21 0x00005617ab860690 in main ()
affects: | ubuntu → libtext-unaccent-perl (Ubuntu) |
tags: | added: xenial |
Changed in libtext-unaccent-perl (Debian): | |
status: | Unknown → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1793113/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]