Re: Debug info for 'this' pointer vanished from 3.1.24 to 3.1.26?

2022-12-16 Thread 'Sam Clegg' via emscripten-discuss 
On Fri, Dec 16, 2022 at 1:21 AM Gregory Propf  wrote:

> I just checked with version 3.1.28 and there's no 'this' pointer there
> either. I also tried 3.1.25 and it looks like 24 --> 25 is the point where
> the pointer died so to speak. So right now, 3.1.24 is the latest I can use.
> I'm using Ubuntu 22.04 on very recent Intel hardware.
>

If you are curious you could bisect furter to find out which set of llvm
changes actually triggered this regression:
https://emscripten.org/docs/contributing/developers_guide.html#bisecting


> On Thursday, December 15, 2022 at 2:14:35 PM UTC-8 Gregory Propf wrote:
>
>> Hello Heejin, As far as a reproducer, you can clone my project
>> https://github.com/gpropf/clarity and do 'make showcase'. Set some
>> breakpoints around line 715 in the method setCppValFromJSVal() in the file
>> ClarityNode.hpp and then change some of the values in the text fields or
>> range controls on the page that the app generates. You should see that
>> 'this' is visible but there's nothing in it. Currently I just rolled back
>> to 3.1.24. I plan on trying some of the versions after 3.1.26 today or
>> tomorrow. - Greg
>>
>> On Thu, Dec 15, 2022 at 11:30 AM Heejin Ahn  wrote:
>>
>>> I think this is likely to be an LLVM upstream problem than wasm-specific
>>> problem. If you have a reproducer, that'd be helpful as well.
>>>
>>> On Wed, Dec 7, 2022 at 1:02 PM Gregory Propf  wrote:
>>>
 Interesting. I didn't know about git bisect before so this is a good
 tool to have. I mainly just wanted to let the devs and users know this was
 happening. Like I said for now I can just use 3.1.24. It won't be a problem
 unless it turns out I can never upgrade beyond that. Unfortunately I don't
 think I'll have time to go through this right now since it sounds like a
 pretty time consuming iterative process.

 On Tuesday, December 6, 2022 at 4:25:53 PM UTC-8 alon...@gmail.com
 wrote:

> Bisection might be useful here, as in theory any LLVM change could
> cause such a difference or a bug. It's pretty simple to bisect using the
> emsdk:
>
>
> https://emscripten.org/docs/contributing/developers_guide.html#bisecting
>
>
> On Tue, Dec 6, 2022 at 4:22 PM Gregory Propf  wrote:
>
>> I just noticed something while debugging a program. A few days ago I
>> migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I
>> only see the literal value of the 'this' pointer but can't see the
>> components of the object. My CFLAGS are still the same: -O0 -g 
>> -std=c++17.
>> For now I'm fine just setting the toolchain back to 3.1.24 but I was
>> curious as to whether others had noticed this or if it's just that I need
>> some additional CFLAGS settings to get that level of debug detail now.
>>
>> - Greg
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "emscripten-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to emscripten-disc...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/emscripten-discuss/4086b3e0-d720-464e-b93f-800adbd514a3n%40googlegroups.com
>> 
>> .
>>
> --
 You received this message because you are subscribed to the Google
 Groups "emscripten-discuss" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to emscripten-disc...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/emscripten-discuss/c5ddd312-87bf-4c53-ba43-c5030298d882n%40googlegroups.com
 
 .

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "emscripten-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to emscripten-disc...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/emscripten-discuss/CALJpS1PxEayjvjr0t9K2_pZua6Epsy0HAwUfyJNLQLpa4RyRiQ%40mail.gmail.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
>

Re: Debug info for 'this' pointer vanished from 3.1.24 to 3.1.26?

2022-12-16 Thread Gregory Propf 
I just checked with version 3.1.28 and there's no 'this' pointer there 
either. I also tried 3.1.25 and it looks like 24 --> 25 is the point where 
the pointer died so to speak. So right now, 3.1.24 is the latest I can use. 
I'm using Ubuntu 22.04 on very recent Intel hardware.

On Thursday, December 15, 2022 at 2:14:35 PM UTC-8 Gregory Propf wrote:

> Hello Heejin, As far as a reproducer, you can clone my project 
> https://github.com/gpropf/clarity and do 'make showcase'. Set some 
> breakpoints around line 715 in the method setCppValFromJSVal() in the file 
> ClarityNode.hpp and then change some of the values in the text fields or 
> range controls on the page that the app generates. You should see that 
> 'this' is visible but there's nothing in it. Currently I just rolled back 
> to 3.1.24. I plan on trying some of the versions after 3.1.26 today or 
> tomorrow. - Greg
>
> On Thu, Dec 15, 2022 at 11:30 AM Heejin Ahn  wrote:
>
>> I think this is likely to be an LLVM upstream problem than wasm-specific 
>> problem. If you have a reproducer, that'd be helpful as well.
>>
>> On Wed, Dec 7, 2022 at 1:02 PM Gregory Propf  wrote:
>>
>>> Interesting. I didn't know about git bisect before so this is a good 
>>> tool to have. I mainly just wanted to let the devs and users know this was 
>>> happening. Like I said for now I can just use 3.1.24. It won't be a problem 
>>> unless it turns out I can never upgrade beyond that. Unfortunately I don't 
>>> think I'll have time to go through this right now since it sounds like a 
>>> pretty time consuming iterative process.
>>>
>>> On Tuesday, December 6, 2022 at 4:25:53 PM UTC-8 alon...@gmail.com 
>>> wrote:
>>>
 Bisection might be useful here, as in theory any LLVM change could 
 cause such a difference or a bug. It's pretty simple to bisect using the 
 emsdk:

 https://emscripten.org/docs/contributing/developers_guide.html#bisecting


 On Tue, Dec 6, 2022 at 4:22 PM Gregory Propf  wrote:

> I just noticed something while debugging a program. A few days ago I 
> migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I 
> only see the literal value of the 'this' pointer but can't see the 
> components of the object. My CFLAGS are still the same: -O0 -g 
> -std=c++17. 
> For now I'm fine just setting the toolchain back to 3.1.24 but I was 
> curious as to whether others had noticed this or if it's just that I need 
> some additional CFLAGS settings to get that level of debug detail now.
>
> - Greg
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to emscripten-disc...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/emscripten-discuss/4086b3e0-d720-464e-b93f-800adbd514a3n%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "emscripten-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to emscripten-disc...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/emscripten-discuss/c5ddd312-87bf-4c53-ba43-c5030298d882n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "emscripten-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to emscripten-disc...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/emscripten-discuss/CALJpS1PxEayjvjr0t9K2_pZua6Epsy0HAwUfyJNLQLpa4RyRiQ%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/09c8be0b-dbc2-49c4-9d2d-d31dc98fccc4n%40googlegroups.com.

Re: Debug info for 'this' pointer vanished from 3.1.24 to 3.1.26?

2022-12-15 Thread Gregory Propf 
Hello Heejin, As far as a reproducer, you can clone my project
https://github.com/gpropf/clarity and do 'make showcase'. Set some
breakpoints around line 715 in the method setCppValFromJSVal() in the file
ClarityNode.hpp and then change some of the values in the text fields or
range controls on the page that the app generates. You should see that
'this' is visible but there's nothing in it. Currently I just rolled back
to 3.1.24. I plan on trying some of the versions after 3.1.26 today or
tomorrow. - Greg

On Thu, Dec 15, 2022 at 11:30 AM Heejin Ahn  wrote:

> I think this is likely to be an LLVM upstream problem than wasm-specific
> problem. If you have a reproducer, that'd be helpful as well.
>
> On Wed, Dec 7, 2022 at 1:02 PM Gregory Propf  wrote:
>
>> Interesting. I didn't know about git bisect before so this is a good tool
>> to have. I mainly just wanted to let the devs and users know this was
>> happening. Like I said for now I can just use 3.1.24. It won't be a problem
>> unless it turns out I can never upgrade beyond that. Unfortunately I don't
>> think I'll have time to go through this right now since it sounds like a
>> pretty time consuming iterative process.
>>
>> On Tuesday, December 6, 2022 at 4:25:53 PM UTC-8 alon...@gmail.com wrote:
>>
>>> Bisection might be useful here, as in theory any LLVM change could cause
>>> such a difference or a bug. It's pretty simple to bisect using the emsdk:
>>>
>>> https://emscripten.org/docs/contributing/developers_guide.html#bisecting
>>>
>>>
>>> On Tue, Dec 6, 2022 at 4:22 PM Gregory Propf  wrote:
>>>
 I just noticed something while debugging a program. A few days ago I
 migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I
 only see the literal value of the 'this' pointer but can't see the
 components of the object. My CFLAGS are still the same: -O0 -g -std=c++17.
 For now I'm fine just setting the toolchain back to 3.1.24 but I was
 curious as to whether others had noticed this or if it's just that I need
 some additional CFLAGS settings to get that level of debug detail now.

 - Greg

 --
 You received this message because you are subscribed to the Google
 Groups "emscripten-discuss" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to emscripten-disc...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/emscripten-discuss/4086b3e0-d720-464e-b93f-800adbd514a3n%40googlegroups.com
 
 .

>>> --
>> You received this message because you are subscribed to the Google Groups
>> "emscripten-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to emscripten-discuss+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/emscripten-discuss/c5ddd312-87bf-4c53-ba43-c5030298d882n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/CALJpS1PxEayjvjr0t9K2_pZua6Epsy0HAwUfyJNLQLpa4RyRiQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CAKdUWHPaqZHnvp4kgfot5X184%2Bn7xG2z0_VaJOrFUD1WSDAOug%40mail.gmail.com.

Re: Debug info for 'this' pointer vanished from 3.1.24 to 3.1.26?

2022-12-15 Thread Heejin Ahn 
I think this is likely to be an LLVM upstream problem than wasm-specific
problem. If you have a reproducer, that'd be helpful as well.

On Wed, Dec 7, 2022 at 1:02 PM Gregory Propf  wrote:

> Interesting. I didn't know about git bisect before so this is a good tool
> to have. I mainly just wanted to let the devs and users know this was
> happening. Like I said for now I can just use 3.1.24. It won't be a problem
> unless it turns out I can never upgrade beyond that. Unfortunately I don't
> think I'll have time to go through this right now since it sounds like a
> pretty time consuming iterative process.
>
> On Tuesday, December 6, 2022 at 4:25:53 PM UTC-8 alon...@gmail.com wrote:
>
>> Bisection might be useful here, as in theory any LLVM change could cause
>> such a difference or a bug. It's pretty simple to bisect using the emsdk:
>>
>> https://emscripten.org/docs/contributing/developers_guide.html#bisecting
>>
>>
>> On Tue, Dec 6, 2022 at 4:22 PM Gregory Propf  wrote:
>>
>>> I just noticed something while debugging a program. A few days ago I
>>> migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I
>>> only see the literal value of the 'this' pointer but can't see the
>>> components of the object. My CFLAGS are still the same: -O0 -g -std=c++17.
>>> For now I'm fine just setting the toolchain back to 3.1.24 but I was
>>> curious as to whether others had noticed this or if it's just that I need
>>> some additional CFLAGS settings to get that level of debug detail now.
>>>
>>> - Greg
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "emscripten-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to emscripten-disc...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/emscripten-discuss/4086b3e0-d720-464e-b93f-800adbd514a3n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/c5ddd312-87bf-4c53-ba43-c5030298d882n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CALJpS1PxEayjvjr0t9K2_pZua6Epsy0HAwUfyJNLQLpa4RyRiQ%40mail.gmail.com.

Re: Debug info for 'this' pointer vanished from 3.1.24 to 3.1.26?

2022-12-07 Thread Gregory Propf 
Interesting. I didn't know about git bisect before so this is a good tool 
to have. I mainly just wanted to let the devs and users know this was 
happening. Like I said for now I can just use 3.1.24. It won't be a problem 
unless it turns out I can never upgrade beyond that. Unfortunately I don't 
think I'll have time to go through this right now since it sounds like a 
pretty time consuming iterative process.

On Tuesday, December 6, 2022 at 4:25:53 PM UTC-8 alon...@gmail.com wrote:

> Bisection might be useful here, as in theory any LLVM change could cause 
> such a difference or a bug. It's pretty simple to bisect using the emsdk:
>
> https://emscripten.org/docs/contributing/developers_guide.html#bisecting
>
>
> On Tue, Dec 6, 2022 at 4:22 PM Gregory Propf  wrote:
>
>> I just noticed something while debugging a program. A few days ago I 
>> migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I 
>> only see the literal value of the 'this' pointer but can't see the 
>> components of the object. My CFLAGS are still the same: -O0 -g -std=c++17. 
>> For now I'm fine just setting the toolchain back to 3.1.24 but I was 
>> curious as to whether others had noticed this or if it's just that I need 
>> some additional CFLAGS settings to get that level of debug detail now.
>>
>> - Greg
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "emscripten-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to emscripten-disc...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/emscripten-discuss/4086b3e0-d720-464e-b93f-800adbd514a3n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/c5ddd312-87bf-4c53-ba43-c5030298d882n%40googlegroups.com.

Re: Debug info for 'this' pointer vanished from 3.1.24 to 3.1.26?

2022-12-06 Thread Alon Zakai 
Bisection might be useful here, as in theory any LLVM change could cause
such a difference or a bug. It's pretty simple to bisect using the emsdk:

https://emscripten.org/docs/contributing/developers_guide.html#bisecting


On Tue, Dec 6, 2022 at 4:22 PM Gregory Propf  wrote:

> I just noticed something while debugging a program. A few days ago I
> migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I
> only see the literal value of the 'this' pointer but can't see the
> components of the object. My CFLAGS are still the same: -O0 -g -std=c++17.
> For now I'm fine just setting the toolchain back to 3.1.24 but I was
> curious as to whether others had noticed this or if it's just that I need
> some additional CFLAGS settings to get that level of debug detail now.
>
> - Greg
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/4086b3e0-d720-464e-b93f-800adbd514a3n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpQ2S0wXeZ%2BgdauGm543s0v4Ux1%2BPLRsO0w5BgXuJ-c7DQ%40mail.gmail.com.

Debug info for 'this' pointer vanished from 3.1.24 to 3.1.26?

2022-12-06 Thread Gregory Propf 
I just noticed something while debugging a program. A few days ago I 
migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I 
only see the literal value of the 'this' pointer but can't see the 
components of the object. My CFLAGS are still the same: -O0 -g -std=c++17. 
For now I'm fine just setting the toolchain back to 3.1.24 but I was 
curious as to whether others had noticed this or if it's just that I need 
some additional CFLAGS settings to get that level of debug detail now.

- Greg

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/4086b3e0-d720-464e-b93f-800adbd514a3n%40googlegroups.com.