Skip to content
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

Closed
guziy opened this issue Oct 1, 2014 · 5 comments
Closed

Debugging code that uses date time module #16

guziy opened this issue Oct 1, 2014 · 5 comments

Comments

@guziy
Copy link
Contributor

guziy commented Oct 1, 2014

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)

screen shot 2014-10-01 at 10 00 27

Do you think it is possible to change the type definitions to make them more debugger friendly?

Cheers

@guziy
Copy link
Contributor Author

guziy commented Oct 1, 2014

I see that gdb-apple has a problem in general with allocatable arrays like tests... So this might be gdb-apple issue..

@milancurcic
Copy link
Member

I am not familiar with these tools, though I am surprised they seem to not
handle datetime well. There isn't really anything fancy in the code, mostly
derived types and type-bound methods.

Can you make a suggestion on changing the type definitions? If it is
feasible and there is obvious benefit from the new design, we can
re-implement things.

Thanks!

On Wed, Oct 1, 2014 at 10:16 AM, Huziy Oleksandr (Sasha) <
notifications@github.com> wrote:

I see that gdb-apple has a problem in general with allocatable arrays like
tests... So this might be gdb-apple issue..


Reply to this email directly or view it on GitHub
#16 (comment)
.

@guziy
Copy link
Contributor Author

guziy commented Oct 1, 2014

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

@milancurcic
Copy link
Member

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) <
notifications@github.com> wrote:

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


Reply to this email directly or view it on GitHub
#16 (comment)
.

@zbeekman
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants