This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/16286] value.string(length = x) broken for common variable length arrays idiom
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 04 Dec 2013 04:13:45 +0000
- Subject: [Bug python/16286] value.string(length = x) broken for common variable length arrays idiom
- Auto-submitted: auto-generated
- References: <bug-16286-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16286
--- Comment #10 from dje at google dot com ---
(In reply to brobecker from comment #9)
> It's something we already do for Ada. We call it varsize limit,
> and I just realized that we forgot to contribute the "set/show"
> commands! In my 13 years at AdaCore, and the few years before that
> as a lambda user, we never had a case where the error triggered
> by this limit was not symptomatic of a real problem - usually
> undefined data.
>
> I think it would be fine to generalize varsize limit core GDB,
> instead of keeping it within ada-lang. I agree it's not perfect,
> like all heuristics, but it's been working really well for us.
I would want an option to any API routine that uses it to turn it off.
If I'm a module writer, I would not want a user-settable option affecting and
possibly breaking my module. The alternative of setting/resetting the option
around API calls would turn off any module writer (I hope :-)).
Otherwise, "works for me".
--
You are receiving this mail because:
You are on the CC list for the bug.