This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

backtrace/1494: info thread changes the frame level


>Number:         1494
>Category:       backtrace
>Synopsis:       info thread changes the frame level
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 22 11:18:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     david@streamline-computing.com
>Release:        5.3 and 6.0
>Organization:
>Environment:

>Description:
Setting the frame to #1 and then doing an 
"info threads" causes the frame to move to level #2
- info surely shouldn't have this side effect??

The following gdb script and C program demonstrate (cc -g test.c, no other options) the problem.


b f
r
up
frame
info threads
frame

void f() {

}

void g() {

   f();

}

void h() {

   g();

}

int main(int argc, char** argv) {

  h();

}


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]