[pkg-apparmor] Bug#799449: Processed: severity of 799449 is serious

Felix Geyer fgeyer at debian.org
Mon Oct 5 21:02:00 UTC 2015


On Mon, 05 Oct 2015 21:27:58 +0200 intrigeri <intrigeri at debian.org> wrote:
> Control: tag -1 + help
> 
> sarnold wants a stracktrace and says: "if you can get it to fail by
> hand, runniung it with gdb ought to do the trick, gdb ./tst_regex ;
> "run" "bt" iiirc.."
> 
> => anyone with access to mips* a porter box can do that and report
> back here. Help is welcome :)

Doesn't look very promising:

minkus% gdb tst_lib
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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 "mips-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from tst_lib...done.
(gdb) run
Starting program: /home/fgeyer/apparmor-2.10/parser/tst_lib
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mips-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt full
#0  0x00000000 in ?? ()
No symbol table info available.
#1  0x005537a0 in _PROCEDURE_LINKAGE_TABLE_ ()
No symbol table info available.
Backtrace stopped: frame did not save the PC


fwiw all parser/tst_* segfault the same way.

Felix



More information about the pkg-apparmor-team mailing list