-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging code that uses date time module #16
Comments
I see that gdb-apple has a problem in general with allocatable arrays like tests... So this might be gdb-apple issue.. |
I am not familiar with these tools, though I am surprised they seem to not Can you make a suggestion on changing the type definitions? If it is Thanks! On Wed, Oct 1, 2014 at 10:16 AM, Huziy Oleksandr (Sasha) <
|
I've asked our analysts to investigate this... If they or me come up with something that could be done I'll get back to you. Are you using something else for debugging? Thanks |
I use write(,) for most debugging :). It's more work but keeps me grounded. Cheers. On Wed, Oct 1, 2014 at 10:24 AM, Huziy Oleksandr (Sasha) <
|
Yes, I find unit tests, integration tests, regression tests, combined with CI tools etc. makes there be very little need for debugging tools. gdb should work... you may want to install Homebrew and upgrade gcc/binutils etc. |
Hi:
This is more a question than an issue. I have trouble debugging code that uses the date time module.
With ddt, compiled with pgi:
whenever I get in the code where manipulations with date time objects occur (maybe reference to fields...), the gdb process starts consuming enormous amount of memory and it consumes it all...
With gdb-apple compiled with gfortran:
eclipse is refusing to show the datetime or timedelta objects (ddt shows the objects but it freezes due to memory issues)
Do you think it is possible to change the type definitions to make them more debugger friendly?
Cheers
The text was updated successfully, but these errors were encountered: