SP Crashing

[Dan McLaughlin]

The problem I have is I don't have access to the symbols for the 3.0.4 SP
release, so I'm having to build my own to get the symbols.   Unless, you
know of somewhere I can find the debug symbols.

--

Thanks,

Dan McLaughlin
Technology Consortium, LLC
dmclaughlin at tech-consortium.com
mobile: 512.633.8086
http://www.tech-consortium.com

NOTICE: This e-mail message and all attachments transmitted with it are for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is strictly prohibited. The contents of this e-mail are
confidential and may be subject to work product privileges. If you are not
the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message.

Need to schedule a meeting??? http://www.tungle.me/DanMcLaughlin


On Sat, Sep 21, 2019 at 4:08 AM Rod Widdowson <rdw at steadingsoftware.com>
wrote:

> It occurred to me overnight that before you go too far down the build
> world (which is very much targeted at "Scott or Rod"), you
> might get something from a remote debug session.
>
> Assuming you have Visual Studio on a different machine:
>
> * Get the Shib symbols onto the machine with visual studio (it will also
> need to be connected to the internet to resolve the MS
> symbols)
> * Get the remote debugging tools installed[1] and started (you'll need to
> run it elevated) on the machine with shibd.
> * On the machine with the symbols and visual studio attach to the
> shibd.exe on the target machine (Debug->Attach to
> process->ConnectionTarget == machine with shibd on it).
> * Break in and make sure that all the symbols are resolving (this will
> take a while as VS downloads the symbols for all the DLL's
> that shibd links again)
> * let it run and when shibd crashes it should break into the debugger and
> you might get a clean stack of what the problem is.
>
> However to set expectations the "new improved heap" that has, I think,
> been in VS since 15 is not (IMO) very helpful on the
> diagnosis front and the classic problem with a heap corruption is that it
> happen very often after the event.
>
> [1] https://visualstudio.microsoft.com/downloads/?q=remote
>
>
> --
> To unsubscribe from this list send an email to
> dev-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20190923/636c1e7d/attachment.html>