public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/17539] inferiors print in reverse order
Date: Tue, 04 Nov 2014 09:17:00 -0000	[thread overview]
Message-ID: <bug-17539-4717-IIAWdW35hq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17539-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17539

--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
I (quickly) audited the "info" sub commands, and GDB is inconsistent on this
issue in several places.  E.g.,

increasing:

(gdb) info breakpoints 
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x00000000004008ad in main at foo.c:81
2       breakpoint     keep y   0x00000000004008ad in main at foo.c:81
3       breakpoint     keep y   0x00000000004008ad in main at foo.c:81
4       breakpoint     keep y   0x00000000004008ad in main at foo.c:81

(gdb) info skip 
Num     Type           Enb What
1       function       y   main
2       function       y   main
3       function       y   main

(gdb) info bookmarks 
   1       0x4008ad    '0'
   2       0x4008ad    '0'
   3       0x4008ad    '0'
   4       0x4008ad    '0'

decreasing:

(gdb) info display 
Auto-display expressions now in effect:
Num Enb Expression
4:   y  1
3:   y  1
2:   y  1
1:   y  1

(gdb) info threads 
  Id   Target Id         Frame 
  3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30
  2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2
(arg=0x0) at foo.c:60
* 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join
(threadid=140737353893632, thread_return=0x0) at pthread_join.c:92

(gdb) info checkpoints 
  3 process 29132 at 0x4008ad, file foo.c, line 81
  2 process 29131 at 0x4008ad, file foo.c, line 81
  1 process 29130 at 0x4008ad, file foo.c, line 81
* 0 Thread 0x7ffff7fc5740 (LWP 29128) (main process) at 0x4008ad, file foo.c,
line 81

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-11-04  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 21:20 [Bug cli/17539] New: " tromey at sourceware dot org
2014-11-04  9:08 ` [Bug cli/17539] " palves at redhat dot com
2014-11-04  9:17 ` palves at redhat dot com [this message]
2015-01-30 13:35 ` gbenson at redhat dot com
2015-10-22 10:04 ` palves at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-17539-4717-IIAWdW35hq@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).