Wind River Support Network

HomeDefectsLIN5-19679
Fixed

LIN5-19679 : CLONE - gdb does not stop at the second breakpoint

Created: Nov 10, 2014    Updated: Dec 19, 2017
Resolved Date: Nov 11, 2014
Previous ID: LINCCM-201
Found In Version: 5.0.1
Fix Version: 5.0.1.21
Severity: Standard
Applicable for: Wind River Linux 5
Component/s: Toolchain

Description

In customer's test,they set two breakpoints at the same place.
gdb stops at the first breakpoint normally,but it does not stop
at the second breakpoint.
Please see the attachments.

  - logMessage.txt /* test log message */
  - test.c         /* test program (sample) */
  - gdb.tb         /* gdb script for testing tbreak */
  - gdb.b          /* gdb script for testing break */

Steps to Reproduce

<test env>

target      <===>  peer
(run gdb)          (run test pg on ssh connection)

1.compile test.c
2.[peer]  ssh target and run test (test.c) 
3.[target]check the pid of test
4.[target]run gdb -p pid -x gdb.tb (or gdb.b)
5.[target]run "c" in gdb
6.[peer]  input "1"
7.[target] check the output in gdb (the second breakpoint's info will be output)
8.[peer]  input "1"
   #gdb should stop after this step(8).

Other Downloads


Live chat
Online