Python 2.2: segmentation fault in test_strftime

Michael Hudson mwh at python.net
Fri Jan 4 12:56:10 CET 2002


Carsten Gaebler <clpy at snakefarm.org> writes:

> Michael Hudson wrote:
> > 
> > Carsten Gaebler <clpy at snakefarm.org> writes:
> 
> > > Python 2.2 (#2, Jan  3 2002, 14:18:23)
> > > [GCC 2.7.2.3] on linux2
> > > Type "help", "copyright", "credits" or "license" for more information.
> > > >>> import calendar
> > > >>> calendar.day_abbr[0]
> > > 'Mon'
> > > >>> calendar.day_abbr[1]
> > > 'Tue'
> > > >>> calendar.day_abbr[2]
> > > Segmentation fault (core dumped)
> > >
> > > Any ideas what this could be?
> > 
> > Nope.  Doesn't crash for me.
> > 
> > What does a backtrace show?  What version of glibc do you have?
> 
> Uhm, excuse my ignorance, but what is a backtrace?

Well, when you get the above "Segmentation fault (core dumped)"
message, there should be a file "core" somewhere, probably in the
directory you build python in.

In this directory run "gdb ./python core" and type "bt" at the prompt.
What you get is a backtrace.

In this case it seems to be irrelevant:

> glibc is 2.0.7. Seems to be broken - if you can call it 'broken':
> strftime() with all fields of the tm struct set to 2 (this is what
> calendar.day_abbr does) segfaults. 

Oops.

> I tested it with a small C program.  I think I can live with that,
> since this is an extremely pathological case.

Certainly, it seems unlikely to be a Python problem...

Cheers,
M.

-- 
  The Programmer's Quick Guide To Python (Time Machine version):
    You try to shoot yourself in the foot, only to realize that
    there's no need, since Guido thoughtfully shot you in the foot 
    years ago.                     -- Nick Mathewson, comp.lang.python



More information about the Python-list mailing list