[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb-cvs
Subject:    src/gdb ChangeLog mi/mi-main.c
From:       palves () sourceware ! org
Date:       2013-08-30 15:37:37
Message-ID: 20130830153737.11716.qmail () sourceware ! org
[Download RAW message or body]

CVSROOT:	/cvs/src
Module name:	src
Changes by:	palves@sourceware.org	2013-08-30 15:37:37

Modified files:
	gdb            : ChangeLog 
	gdb/mi         : mi-main.c 

Log message:
	MI -trace-find, print frame with LOC_AND_ADDRESS instead of SRC_AND_LOC.
	
	When I looked for print_stack_frame calls in MI, I wondered why this
	one passing down SRC_AND_LOC.  print_stack_frame does:
	
	/* For mi, alway print location and address.  */
	if (ui_out_is_mi_like_p (current_uiout))
	print_what = LOC_AND_ADDRESS;
	
	So it really doesn't matter which value is passed down, but, to avoid
	confusion in readers, it's better to use the MI standard here.
	There's another SRC_AND_LOC in mi-interp.c, but that one makes sense.
	
	gdb/
	2013-08-30  Pedro Alves  <palves@redhat.com>
	
	* mi/mi-main.c (mi_cmd_trace_find): Use LOC_AND_ADDRESS instead of
	SRC_AND_LOC.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.15956&r2=1.15957
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/mi/mi-main.c.diff?cvsroot=src&r1=1.239&r2=1.240

[prev in list] [next in list] [prev in thread] [next in thread]