how to crash report?

May 15, 2008 at 4:00pm

how to crash report?

hi all. sorry for the silly question, but how does one go about logging a crash report? im getting strange crashes on seemingly mundane tasks..

is it better to post results here or to c74 support?

thanks
r

#37803
May 16, 2008 at 11:14am

Do one or the other, but not both. Tech support tracks the list and they don’t like to get the same report twice.

If you think the bug may be likely to bite others, then by all means here. OTOH, if you think it’s something so exotic it won’t happen to anyone else… you’re probably wrong.-) If your demo patch contains highly proprietary stuff you don’t want to publicize, then you might want to report directly to TS.

Also, be sure to check the Bug Report guidelines, which have been posted about 2,147,483,648 times to the list, at which point I stopped counting;- They do make the bug report process more productive for everybody (even if there’s some work involved at your end).

HtH,
P.

#130821
May 16, 2008 at 11:27am

cool thanks for the reply.. i have been searching for info on how to actually perform a report. couldnt find anything in the manual :

and im still looking online here

#130822
May 16, 2008 at 1:55pm

Google is your friend.

http://www.google.de/search?q=bug+report+guidelines+site%3Acycling74.com

OK, I exaggerated a little. It’s only 120 hits;-

You’re right that this is not in the RefMan (at least, I don’t think it’s in there). If you feel that is where it ought to be, you might want to mention that in a message with a Subject: line that is likely to catch the documentation team’s collective eye, something like “Documentation Request”. Maybe wait a day or so to see if Gregory Taylor & his cohorts reply to this thread… they, too, track the list, but there is still a lot of Max5 stuff taking up their time.

#130823
May 16, 2008 at 8:05pm

thanks for that..

although i am still trying to see where and how to find the crash reports?

:)

#130824
May 16, 2008 at 9:40pm

On 16 mai 08, at 22:05, chrome-metronome wrote:

> thanks for that..
>
> although i am still trying to see where and how to find the crash
> reports?

You can send report to support [at] cycling74 [dot] com

ej

#130825
May 16, 2008 at 9:47pm

:)

but how do i get the report ???

thanks

#130826
May 17, 2008 at 10:02am

If you mean the Crash Log…

~/Library/Logs/Crash Reporter/MaxMSP.crash.log

or open up Console, click open the Logs tab, and navigate as above.

#130827
May 19, 2008 at 2:37pm

Peter Castine schrieb:
> Also, be sure to check the Bug Report guidelines, which have been
> posted about 2,147,483,648 times to the list, at which point I
> stopped counting;-

it reached 4294967296 shortly after btw. after that I had to go into
float territory and completely lost precision…


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com

#130828
May 19, 2008 at 5:23pm

Quote: Stefan Tiedje wrote on Mon, 19 May 2008 08:37
—————————————————-
after that I had to go into
> float territory and completely lost precision…

midgets have feelings to you know!

thanks for the help. it was exactly what i needed.

#130829
May 19, 2008 at 7:45pm

Quote: Peter Castine wrote on Sat, 17 May 2008 04:02
—————————————————-
> If you mean the Crash Log…
>
> ~/Library/Logs/Crash Reporter/MaxMSP.crash.log
>
> or open up Console, click open the Logs tab, and navigate as above.
—————————————————-

is this just for Mac? any ideas for XP pro?

thanks again

#130830
May 20, 2008 at 9:07am

Quote: rory.stjohn@gmail.com wrote on Mon, 19 May 2008 21:45
—————————————————-
> Quote: Peter Castine wrote on Sat, 17 May 2008 04:02
> —————————————————-
> > If you mean the Crash Log…
> >
> > ~/Library/Logs/Crash Reporter/MaxMSP.crash.log
> >
> > or open up Console, click open the Logs tab, and navigate as above.
> —————————————————-
>
> is this just for Mac? any ideas for XP pro?
>
> thanks again
>
—————————————————-

If you want information for a particular system, it is a Good Idea to say so up front rather than make people guess. It saves a lot of time and effort for the people who are trying to help you.

I have been told that XP will leave some kind of crash report on your desktop, but I’ve never found the durn thing. It may be that you need some particular version of a DLL for this to happen, but I don’t know for sure.

What I have been able to do is, while the crash report dialog is still open (“Do you want to send the crash information to Microsoft?”), you can go into the temp folder and make a copy of the crash info. The original file is deleted immediately after closing the dialog.

#130831
May 20, 2008 at 10:10am

thanks for the reply..

when i was first posting, i thought the crash log was a feature of Max itself, but just couldnt find anything on it.

sorry anyway. i have since got in touch with support with my patch.
thanks for the help.

#130832
May 20, 2008 at 11:07am

chrome-metronome schrieb:
> is this just for Mac? any ideas for XP pro?

As far as I know Microsoft designed crashreports in an unusable
uninformative way, they don’t seem to help anyway…
Just concentrate on collecting as much information as possible to make
the crash reproducible. I guess if it crashes on Mac its helpful to
resolve issues on Windows as well if you have a Mac crashreport…

(I guess one of the reasons for Windows programmers to create a cross
platform version of their software, is to find the bugs easier…;-)

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com

#130833
May 20, 2008 at 1:04pm

Microsoft crash reports are called minidump files (.dmp). They actually can be a very useful tool for helping debug crashes in the field. However, for various reasons they are not useful to us for Max on windows at this point in time.

Anyway, if you are experiencing a reproducible crash on windows (or mac for that matter) please do your best to provide us with steps to reproduce the crash. Any time we can reproduce a crash on mac or windows it makes fixing the problem much much easier.

Thanks,
Rob

#130834

You must be logged in to reply to this topic.