[Python-Dev] pdb segfaults in 2.5 trunk? (original) (raw)
Jeremy Hylton jeremy at alum.mit.edu
Mon Apr 10 21:43:05 CEST 2006
- Previous message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Next message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
4On 4/10/06, Jeremy Hylton <jeremy at alum.mit.edu> wrote:
On 4/10/06, Phillip J. Eby <pje at telecommunity.com> wrote: > Is anybody else getting this?
Neal had originally reported that testtrace failed with a segfault, and it's essentially exercising the same code. I don't see a failure there or here at the moment. If there is a bug, though, it's likely to be in the line number table that the new compiler generates.
> > Python 2.5a1 (trunk:45237, Apr 10 2006, 15:25:33) > [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import pdb > >>> def x(): > ... if 'a' in 'b': > ... pass > ... > >>> pdb.run("x()") > > (1)() > (Pdb) s > --Call-- > > (1)x() > (Pdb) s > > (2)x() > (Pdb) s > Segmentation fault > > It usually happens within a few 's' operations in pdb. >>> def x(): ... if 'a' in 'b': ... pass ... [34945 refs] >>> pdb.run('x()') > (1)()->None (Pdb) s --Call-- > (1)x() (Pdb) s --Return-- > (1)x()->None (Pdb) s --Return-- > (1)()->None (Pdb) s [35023 refs] >>> [35023 refs] [11168 refs] Will try with a non-debug build soon.
I don't see it in a non-debug build either. Python 2.5a1 (trunk:43632M, Apr 10 2006, 15:41:31) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
Jeremy
- Previous message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Next message: [Python-Dev] pdb segfaults in 2.5 trunk?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]