Linaro GDB

gdb.base/foll-vfork.exp failure

Bug #684564 reported by Yao Qi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro GDB
Confirmed
Low
Ulrich Weigand

Bug Description

Running ../../../gdb-linaro/gdb/testsuite/gdb.base/foll-vfork.exp ...
FAIL: gdb.base/foll-vfork.exp: vfork parent follow, finish after tcatch vfork
FAIL: gdb.base/foll-vfork.exp: vfork child follow, finish after tcatch vfork

Find this message below near these two failures,

 Cannot insert breakpoint 0.^M
 Error accessing memory address 0xe8: Input/output error.

Further analysis is needed.

Tags: testsuite
Revision history for this message
Ulrich Weigand (uweigand) wrote :

Note that this problem does not occur if glibc debuginfo is installed.

However, even *with* the fix for #661253 (ARM unwind info), the problem still persists; I haven't yet understood why exactly.

Michael Hope (michaelh1)
summary: - Failures gdb.base/foll-vfork.exp
+ gdb.base/foll-vfork.exp failure
tags: added: testsuite
Ulrich Weigand (uweigand)
Changed in gdb-linaro:
status: New → Confirmed
importance: Undecided → Low
Ulrich Weigand (uweigand)
Changed in gdb-linaro:
assignee: nobody → Ulrich Weigand (uweigand)
Revision history for this message
Ulrich Weigand (uweigand) wrote :

This is another instance of the problem that GDB is often unable to backtrace out of glibc system call stubs. Duplicate to #684218.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.