Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #72282 > unrolled thread
| Started by | dieter <dieter@handshake.de> |
|---|---|
| First post | 2014-05-30 09:04 +0200 |
| Last post | 2014-05-30 09:04 +0200 |
| Articles | 1 — 1 participant |
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.
Re: Script suddenly stops dieter <dieter@handshake.de> - 2014-05-30 09:04 +0200
| From | dieter <dieter@handshake.de> |
|---|---|
| Date | 2014-05-30 09:04 +0200 |
| Subject | Re: Script suddenly stops |
| Message-ID | <mailman.10476.1401433473.18130.python-list@python.org> |
Chris <ch2009@arcor.de> writes:
> I'm trying to read ten 200 MB textfiles into a MySQL MyISAM database
> (Linux, ext4). The script output is suddenly stopping, while the Python
> process is still running (or should I say sleeping?). It's not in top,
> but in ps visible.
>
> Why is it stopping? Is there a way to make it continue, without calling
> "kill -9", deleting the processed lines and starting it again?
This is difficult to say (from the distance).
I would approach an analysis in the following way:
* use a Python with debug symbols (OS provided Python installations
usually lack debugging symbols; a manually generated
Python usually has those symbols)
* run your script unter "gdb" control (the C level debugger)
* when you see that your script starts "sleeping",
hit "CTRL-C" in the "gdb" session
* use "gdb" commands - maybe combined with the special
python commands for "gdb" to learn where the "sleeping"
happens.
These special Python commands allow you to use
the C level debugger "gdb" to get information about
the Python level.
Back to top | Article view | comp.lang.python
csiph-web