This is the mail archive of the gdb-patches@sourceware.org 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]

Re: [RFC][Python] gdbpy_frame_stop_reason_string bug

From: Tom Tromey <tromey at redhat dot com>
To: Kevin Pouget <kevin dot pouget at gmail dot com>
Cc: Pedro Alves <pedro at codesourcery dot com>, pmuldoon at redhat dot com, gdb-patches at sourceware dot org
Date: Wed, 12 Oct 2011 11:05:56 -0600
Subject: Re: [RFC][Python] gdbpy_frame_stop_reason_string bug
References: <CAPftXULjbKonB=-YneTVg+jeZiUDUruqtjrTighL8dgXTWoo_g@mail.gmail.com> <201110121552.29096.pedro@codesourcery.com> <CAPftXUJ_cfH=jX4CVjokXpJpJfNkPF4OCgLceNitbnPbnrQ+Mg@mail.gmail.com>

>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:

>> Why not use the supplied gdb constants in this case?  "2" does not map
>> to any enum.
>> IE gdb.FRAME_UNWIND_NO_REASON

Kevin> it looks like these enums are not documented, are they? I can't grep
Kevin> 'FRAME_UNWIND_NO_REASON' in gdb.texinfo

Yeah, we should document those.
I filed: http://sourceware.org/bugzilla/show_bug.cgi?id=13285

Tom

References:
- [RFC][Python] gdbpy_frame_stop_reason_string bug
  - From: Kevin Pouget
- Re: [RFC][Python] gdbpy_frame_stop_reason_string bug
  - From: Pedro Alves
- Re: [RFC][Python] gdbpy_frame_stop_reason_string bug
  - From: Kevin Pouget

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