That worked great, thank you!
Steve
On Fri, Mar 27, 2015 at 8:58 AM Xavier de Gaye <[email protected]> wrote:
> On 03/26/2015 03:48 PM, Steve Herrell wrote:
> > I'm seeing a python back trace when I attempt to debug from a core dump
> file.
>
>
> Hi Steve,
>
> Thanks for this exhaustive report.
> The backtrace is the same as the one that occured in issue #6:
> "Pyclewn crashes when trying to attach to a remote gdb" at:
>
> https://bitbucket.org/xdegaye/pyclewn/issue/6
>
> The cause is that the thread name is unknown to gdb both when connecting to
> the target using gdbserver or in your test case with a core file. And
> Pyclewn
> did not handle that correctly. Issue #6 has been fixed and your core file
> test
> case does not crash anymore on the current development version.
>
> The next Pyclewn version 2.1 should be released at the end of next week.
> Otherwise, you can build Pyclewn from the BitBucket repository by cloning
> it
> with:
>
> hg clone https://[email protected]/xdegaye/pyclewn
>
> And reading the section named "Installing from the development version at
> BitBucket" of the INSTALL file found in the local repository that you just
> cloned.
>
>
> > Many thanks for a great program,
>
> Thanks, this is nice to know.
>
> Xavier
>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
