public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "asmwarrior at gmail 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: Mon, 21 Jun 2010 02:42:00 -0000	[thread overview]
Message-ID: <20100621024212.30680.qmail@sourceware.org> (raw)
In-Reply-To: <20100320163108.11407.niko.sams@gmail.com>


------- Additional Comments From asmwarrior at gmail dot com  2010-06-21 02:42 -------
Hi, here is my modified source code of gdb/stack.c
it is around the line 1469, and then change the function to like this below:
-------------------------

static void
iterate_over_block_locals (struct block *b,
               iterate_over_block_arg_local_vars_cb cb,
               void *cb_data)
{
  struct dict_iterator iter;
  struct symbol *sym;
  struct frame_info *frame;
  struct symtab_and_line sal;
  frame = get_selected_frame (NULL) ;
  find_frame_sal (frame, &sal);

  ALL_BLOCK_SYMBOLS (b, iter, sym)
    {
      switch (SYMBOL_CLASS (sym))
    {
    case LOC_LOCAL:
    case LOC_REGISTER:
    case LOC_STATIC:
    case LOC_COMPUTED:
      if (SYMBOL_IS_ARGUMENT (sym))
        break;
      if(sym->line>= sal.line)
        break;
      (*cb) (SYMBOL_PRINT_NAME (sym), sym, cb_data);
      break;

    default:
      /* Ignore symbols which are not locals.  */
      break;
    }
    }
} 

---------------------------------

Asmwarrior ollydbg from codeblocks' forum



-- 


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.


  parent reply	other threads:[~2010-06-21  2:42 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 ` jens dot elmenthaler at verigy dot com
2010-03-31 13:23 ` pmuldoon at redhat 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 [this message]
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=20100621024212.30680.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).