public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11407] -stack-list-locals should catch python exceptions and return the error per variable
Date: Wed, 31 Mar 2010 13:23:00 -0000 [thread overview]
Message-ID: <20100331132321.20212.qmail@sourceware.org> (raw)
In-Reply-To: <20100320163108.11407.niko.sams@gmail.com>
------- Additional Comments From jens dot elmenthaler at verigy dot com 2010-03-31 13:23 -------
(In reply to comment #5)
> Does setting
> help maintenance set python print-stack off
> help in this circumstance?
No. Here is what I get:
688,131 37-interpreter-exec console "maintenance set python print-stack off"
688,133 37^done
688,134 (gdb)
689,771 38-exec-next --thread 1 1
689,773 38^running
689,776 *running,thread-id="all"
689,776 (gdb)
689,779 *stopped,reason="end-stepping-range",frame=
{addr="0x0000000000400fce",func="main",args=[],fi\
le="../src/sneha.cpp",fullname="/home/jelmenth/Projects/ws-dsf-
test/sneha/src/sneha.cpp",line="60"},\
thread-id="1",stopped-threads="all",core="1"
689,779 (gdb)
689,821 39-stack-list-locals --thread 1 --frame 0 1
689,824 39^error,msg="Cannot access memory at address 0x64697469617700"
689,826 (gdb)
689,828 40-stack-info-depth --thread 1 5
689,829 40^done,depth="1"
689,830 (gdb)
------- Additional Comments From pmuldoon at redhat dot com 2010-03-31 13:23 -------
Created an attachment (id=4692)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4692&action=view)
Mi errors output
I attached the output with the stack listing turned off? In this view you only
see the locals output?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11407
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-03-31 13:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 16:31 [Bug python/11407] New: " niko dot sams at gmail dot com
2010-03-20 20:00 ` [Bug python/11407] " niko dot sams at gmail dot com
2010-03-20 20:41 ` msnkipa at mail dot ru
2010-03-22 7:11 ` jens dot elmenthaler at verigy dot com
2010-03-25 9:15 ` jens dot elmenthaler at verigy dot com
2010-03-25 9:32 ` jens dot elmenthaler at verigy dot com
2010-03-30 15:31 ` jens dot elmenthaler at verigy dot com
2010-03-31 13:07 ` pmuldoon at redhat dot com
2010-03-31 13:09 ` pmuldoon at redhat dot com
2010-03-31 13:23 ` pmuldoon at redhat dot com [this message]
2010-03-31 13:23 ` jens dot elmenthaler at verigy dot com
2010-03-31 13:45 ` jens dot elmenthaler at verigy dot com
2010-03-31 14:47 ` pmuldoon at redhat dot com
2010-03-31 14:58 ` jens dot elmenthaler at verigy dot com
2010-03-31 15:12 ` pmuldoon at redhat dot com
2010-04-01 12:39 ` pmuldoon at redhat dot com
2010-04-01 12:40 ` pmuldoon at redhat dot com
2010-04-05 13:23 ` marc at khouzam dot com
2010-04-05 13:54 ` pmuldoon at redhat dot com
2010-04-07 7:26 ` jens dot elmenthaler at verigy dot com
2010-04-07 17:10 ` jan dot kratochvil at redhat dot com
2010-04-07 17:29 ` pmuldoon at redhat dot com
2010-05-05 15:56 ` jan dot kratochvil at redhat dot com
2010-06-18 0:25 ` asmwarrior at gmail dot com
2010-06-18 8:21 ` asmwarrior at gmail dot com
2010-06-18 8:36 ` pmuldoon at redhat dot com
2010-06-18 9:57 ` pmuldoon at redhat dot com
2010-06-18 10:25 ` pmuldoon at redhat dot com
2010-06-19 3:23 ` asmwarrior at gmail dot com
2010-06-19 4:04 ` asmwarrior at gmail dot com
2010-06-19 8:10 ` pmuldoon at redhat dot com
2010-06-19 8:29 ` pmuldoon at redhat dot com
2010-06-19 8:40 ` asmwarrior at gmail dot com
2010-06-19 9:02 ` pmuldoon at redhat dot com
2010-06-19 12:34 ` asmwarrior at gmail dot com
2010-06-20 3:20 ` asmwarrior at gmail dot com
2010-06-20 6:14 ` asmwarrior at gmail dot com
2010-06-20 7:11 ` asmwarrior at gmail dot com
2010-06-20 7:17 ` pmuldoon at redhat dot com
2010-06-21 2:29 ` asmwarrior at gmail dot com
2010-06-21 2:42 ` asmwarrior at gmail dot com
2010-06-21 19:24 ` tromey at redhat dot com
2010-06-28 17:15 ` [Bug mi/11407] " pmuldoon at redhat dot com
2010-09-16 13:50 ` pmuldoon at redhat dot com
2010-09-16 13:51 ` pmuldoon 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=20100331132321.20212.qmail@sourceware.org \
--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).