Skip to Content.
Sympa Menu

charm - Re: [charm] [ppl] backtraces

charm AT lists.cs.illinois.edu

Subject: Charm++ parallel programming system

List archive

Re: [charm] [ppl] backtraces


Chronological Thread 
  • From: Phil Miller <mille121 AT illinois.edu>
  • To: Jonathan Lifflander <jliffl2 AT illinois.edu>
  • Cc: charm AT cs.uiuc.edu
  • Subject: Re: [charm] [ppl] backtraces
  • Date: Mon, 29 Jul 2013 15:23:39 -0500
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/charm/>
  • List-id: CHARM parallel programming system <charm.cs.uiuc.edu>

That's the kind of failure that happens when some entry methods don't get registered by inclusion of the appropriate module thought the extern mechanism or -module too on the linker command line. The code compiles because the decl files include all the necessary declarations, and presumably linked with the relevant objects directly, but without the generated code to register at startup.

On Jul 29, 2013 3:56 PM, "Jonathan Lifflander" <jliffl2 AT illinois.edu> wrote:
Normal GDB backtraces are not very useful when the system is
delivering a message and fails. To ameliorate this, we have developed
a tool called CharmDebug which allows you to inspect the queue on each
processor, change the order of delivery, etc.

Here is the link to the research area on our website, where you can
find many papers:

https://charm.cs.illinois.edu/research/parallel_debug

The software is available to download on the website under the software section.

I'm not exactly sure how a missing extern (which should be caught at
link time), ended up producing a runtime error. Could you provide a
little more information?

Thanks,

Jonathan

On Mon, Jul 29, 2013 at 2:41 PM, Nicolas Bock <nicolasbock AT gmail.com> wrote:
> It turns out that this particular problem was caused by a missing "extern
> module ...;" statement in one of the interface files. As a feature request:
> it would be great if the compiler caught omissions like these.
>
> Thanks,
>
> nick
>
>
> On Mon, Jul 29, 2013 at 12:13 PM, Nicolas Bock <nicolasbock AT gmail.com>
> wrote:
>>
>> Hi,
>>
>> I keep getting segfaults deep inside the RTS. Unfortunately I haven't
>> found a good way yet to connect the backtraces to my code, since the
>> callstack doesn't actually involve anything from my code. Is there a
>> recommended technique to debug these kinds of situations?
>>
>> Thanks,
>>
>> nick
>>
>
>
> _______________________________________________
> charm mailing list
> charm AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/charm
>
_______________________________________________
charm mailing list
charm AT cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/charm
_______________________________________________
ppl mailing list
ppl AT cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/ppl



Archive powered by MHonArc 2.6.16.

Top of Page