pdb bug and questions

[R. Bernstein]

castironpi <castironpi at gmail.com> writes:

> On Sep 4, 4:22 pm, Stef Mientki <stef.mien... at gmail.com> wrote:
>> hello,
>>
>> I'm trying to embed a debugger into an editor.
>> I'm only interested in high level debugging.
>> The first question is what debugger is the best for my purpose ?
>> (pdb, pydb, rpdb2, smart debugger, extended debugger ?
>>
>> Second question, in none of the above debuggers (except rpdb2),
>> I can find a  "break now",
>> so it seems impossible to me to detect unlimited while loops ?
>>
>> For the moment I started with pdb, because most of the debuggers seems
>> to be an extension on pdb.
>> When I launch the debugger ( winXP, Python 2.5) from with my editor
>>   python -u -m pdb  D:\\Data\\test_IDE.py
>> I get this error
>>   IOError: (2, 'No such file or directory', 'D:\\Data\test_IDE.py')
>> NOTICE 1 backslash ----------------------------------^
>>
>> If I launch the debugger with
>>   python -u -m pdb  D:/Data/test_IDE.py
>> It runs fine.
>>
>> This looks like a bug to me.
>> What's the best way to report these kind of bugs ?
>>
>> Although I mostly use os.path.join to be OS independent,
>> these kind of bugs give me the impression,
>> that I can better do the join myself and always use forward slashes.
>> Is this a valid conclusion ?
>>
>> thanks,
>> Stef Mientki
>
> Stef,
>
> I discovered the same problem too with my editor.  I solved it by
> using only the file name, and setting the initial directory on the
> executable.

I don't know if this helps, but in pydb there is an option to set the
initial directory the debugger works in. Inside the debugger there is
the gdb command "cd".