Debug symbols Topic is solved

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
User avatar
CrouZ
Moongazer
Moongazer
Posts: 11
Joined: 2019-07-05, 10:39

Debug symbols

Unread post by CrouZ » 2022-10-28, 08:30

I cannot find debug symbols for the latest releases on this page: https://archive.palemoon.org/symbols/
Have they moved somewhere else?

The reason I ask is that since 2022-09-28 when I updated to v31.3.0, pale moon started crashing a few times a day, and I wanted see if I can get any hints from the call stack.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35473
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: Debug symbols

Unread post by Moonchild » 2022-10-28, 09:54

I just forgot to upload them. Oops on me!
Doing so now.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
CrouZ
Moongazer
Moongazer
Posts: 11
Joined: 2019-07-05, 10:39

Re: Debug symbols

Unread post by CrouZ » 2023-01-04, 12:03

Thank you!

I finally had a look into this and it appears to be proxy related (crash for v31.4.2):

Code: Select all

 	26c12d2f()	Unknown
 	[Frames below may be incorrect and/or missing]	Unknown
 	[Inline Frame] xul.dll!EnterIon(JSContext *) Line 2849	C++
 	xul.dll!js::jit::IonCannon(JSContext * cx, js::RunState & state) Line 2947	C++
 	xul.dll!js::RunScript(JSContext * cx, js::RunState & state) Line 399	C++
 	xul.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 500	C++
 	xul.dll!InternalCall(JSContext * cx, const js::AnyInvokeArgs & args) Line 524	C++
 	xul.dll!js::Call(JSContext * cx, JS::Handle<JS::Value> fval, JS::Handle<JS::Value> thisv, const js::AnyInvokeArgs & args, JS::MutableHandle<JS::Value> rval) Line 543	C++
 	xul.dll!JS_CallFunctionName(JSContext * cx, JS::Handle<JSObject *> obj, const char * name, const JS::HandleValueArray & args, JS::MutableHandle<JS::Value> rval) Line 2872	C++
>	xul.dll!mozilla::net::ProxyAutoConfig::GetProxyForURI(const nsCString & aTestURI, const nsCString & aTestHost, nsACString_internal & result) Line 832	C++
 	[Inline Frame] xul.dll!mozilla::net::nsPACMan::ProcessPending() Line 617	C++
 	xul.dll!mozilla::net::nsPACMan::ProcessPendingQ() Line 559	C++
 	[Inline Frame] xul.dll!mozilla::net::nsPACMan::PostQuery(mozilla::net::PendingPACQuery *) Line 378	C++
 	xul.dll!mozilla::net::PendingPACQuery::Run() Line 278	C++
 	xul.dll!nsThread::ProcessNextEvent(bool aMayWait, bool * aResult) Line 1146	C++
 	xul.dll!NS_ProcessNextEvent(nsIThread * aThread, bool aMayWait) Line 355	C++
 	xul.dll!mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate * aDelegate) Line 367	C++
 	[Inline Frame] xul.dll!MessageLoop::RunInternal() Line 228	C++
 	xul.dll!MessageLoop::RunHandler() Line 222	C++
 	xul.dll!MessageLoop::Run() Line 202	C++
 	xul.dll!nsThread::ThreadFunc(void * aArg) Line 460	C++
 	[External Code]	
After switching to using Manual proxy configuration it has not crashed again.

I'm not comfortable posting the dump file for my main profile in the forum, but I could PM it if you want to have a look.
Otherwise, I'll see if I can repeat the issue with a clean profile.

Locked