[Octave-bug-tracker] [bug #60531] dbstack(N) not omitting innermost frames as it should

[John W. Eaton]

Follow-up Comment #8, bug #60531 (project octave):

The ambiguity occurs when there is no idx_vector(int) constructor and there is
no best choice when the options are char, long int, and pointer to
idx_base_rep.  You can see the same behavior with the following simple
example:


class foo
{
public:
  foo (char c) { }
  // foo (int i) { }
  foo (long int li) { }
  foo (void *p) { }
};

int main (void)
{
  foo x (0);
  return 0;
}


For idx_vector, this problem can happen when octave_idx_type and F77_INT are
both int64_t.  It doesn't happen if F77_INT is int.

I pushed the following change to ensure that there is always an
idx_vector(int) constructor defined:

http://hg.savannah.gnu.org/hgweb/octave/rev/b36e83cdbf05

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60531>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/