Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #72677 > unrolled thread

Re: Missing stack frames?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Missing stack frames? Nikolaus Rath <Nikolaus@rath.org> - 2014-06-04 21:10 -0700
    Re: Missing stack frames? Paul Rubin <no.email@nospam.invalid> - 2014-06-04 22:22 -0700
      Re: Missing stack frames? Nikolaus Rath <Nikolaus@rath.org> - 2014-06-05 18:23 -0700

#72677 — Re: Missing stack frames?

Chris Angelico <rosuav@gmail.com> writes:
> On Wed, Jun 4, 2014 at 12:30 PM, Nikolaus Rath <Nikolaus@rath.org> wrote:
>> I've instrumented one of my unit tests with a conditional
>> 'pdb.set_trace' in some circumstances (specifically, when a function is
>> called by a thread other than MainThread).
>
> I think the likelihood of this being an issue with interactive
> debugging and threads is sufficiently high that you should avoid
> putting the two together, at least until you can verify that the same
> problem occurs without that combination.

Here's stacktrace as obtained by traceback.print_stack():

tests/t1_backends.py:563: test_extra_data[mock_s3c-zlib] PASSED
tests/t1_backends.py:563: test_extra_data[mock_s3c-bzip2] PASSED

======================== 87 tests deselected by '-kextra' =========================
=============== 5 passed, 1 skipped, 87 deselected in 0.65 seconds ================
  File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/common.py", line 853, in close
    self.fh.close()
  File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/s3c.py", line 691, in close
    traceback.print_stack(file=sys.stdout)
something is wrong
  File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/common.py", line 853, in close
    self.fh.close()
  File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/s3c.py", line 691, in close
    traceback.print_stack(file=sys.stdout)
something is wrong
  File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/common.py", line 1050, in close
    self.fh.close()
  File "/home/nikratio/in-progress/s3ql/src/s3ql/backends/s3c.py", line 691, in close
    traceback.print_stack(file=sys.stdout)


Still no context before the ominous close() call. I'm very confused.


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

[toc] | [next] | [standalone]

#72680

Nikolaus Rath <Nikolaus@rath.org> writes:
> Still no context before the ominous close() call. I'm very confused.

close() could be getting called from a destructor as the top level
function of a thread exits, or something like that.

[toc] | [prev] | [next] | [standalone]

#72805

Paul Rubin <no.email@nospam.invalid> writes:
> Nikolaus Rath <Nikolaus@rath.org> writes:
>> Still no context before the ominous close() call. I'm very confused.
>
> close() could be getting called from a destructor as the top level
> function of a thread exits, or something like that.

Shouldn't the destructor have its own stack frame then, i.e. shouldn't
the first frame be in a __del__ function?

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web