Summary: | memmem crash | ||
---|---|---|---|
Product: | glibc | Reporter: | Jan Kratochvil <jan> |
Component: | libc | Assignee: | Maxim Kuvyrkov <maxim.kuvyrkov> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | allan, drepper.fsp, eblake, hjl.tools, jan, law, maxim.kuvyrkov, ppluzhnikov |
Priority: | P2 | Flags: | fweimer:
security-
|
Version: | 2.17 | ||
Target Milestone: | 2.17 | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | 14602 | ||
Bug Blocks: | |||
Attachments: |
GDB debug output
.tar.xz of core file, gdb binary, rpm -qa (Fedora Rawhide 2012-10-12) .c crash reproducer. |
Description
Jan Kratochvil
2012-10-13 18:47:01 UTC
Created attachment 6684 [details]
.tar.xz of core file, gdb binary, rpm -qa (Fedora Rawhide 2012-10-12)
Reproduced it with FSF GDB HEAD: cd gdb/testsuite; while runtest gdb.base/find.exp;do :;done According to logs crashes also: gdb.python/py-inferior.exp Can you provide GDB command line option to trigger this? You can use a memmem wrapper to extract a testcase: 1. Copy simple_memmem from string/test-memmem.c in glibc. 2. Write a function to dump memmem input into a C source code, including address values. 3. Call simple_memmem to get correct result. 4. Compare result from memmem against simple_memmem. If it fails, call the dumper to generate the testcase. 4. Link GDB against the memmem wrapper. You can generate a testcase by 1. Dumper called on wrong result from memmem. 2. Run dumper by hand inside GDB when GDB segfaults Created attachment 6685 [details]
.c crash reproducer.
Fixed in e9f372520618161d7d73e028ca23818e83b88bbc. |