| Message |
 |
- Date: 2010-11-24 16:12
- Sender: Nathan Letwory
- Don't forget to attach all required files and information (as told on the submission page).
|
|
- Date: 2010-11-24 16:20
- Sender: Dusan Maliarik
- Hi Nathan, thanks for quick reaction. I don't intend to become blender developer, I'm time poor and my C skills are.. are not. Yes I can make a debug build of blender, but that's not the point of this ticket.
If some importer fails (if anything fails for that matter), users with non-debug build should be able to get detailed information about that failure, so they can either report bug to blender, or fix those files that are being imported.
|
- Date: 2010-11-24 18:20
- Sender: Brecht Van Lommel
- Well, that's just a difference between C and python code, there is no solution for getting debug information besides making a debug build...
Please attach a .dae file that fails and mention the exact blender version/revision and operating system you use.
|
- Date: 2010-11-24 18:30
- Sender: Dusan Maliarik
- Hallo Brecht, I don't agree that there's no way to get that debug information. Correct me if I'm wrong, but most software use loggers, which can be set to different log levels. Assuming that the importer logs meaningful messages when there's some issue with the input, why wouldn't we be able to read this?
I won't attach any DAE file, it doesn't matter what's wrong with my particular data. I already fixed my DAE producing code.
|
- Date: 2010-11-24 18:40
- Sender: Jan Diederich
- "Please attach a .dae file that fails and mention the exact blender version/revision and operating system you use."
That's not really his point, he wants the old debug power without having programmer skills.
But nevertheless, you are right at another point: The only solution now (with the C++ code) is: Use at least a debug build - which you can download from graphicall.org, and there you should get some more debug info.
|
- Date: 2010-11-24 18:44
- Sender: Jan Diederich
- Oh, and I forget: Attaching a .dae file to reproduce the failure would be great... But most error reporters refuse that. So that we have a hard time helping them, and also dampened interest resolving that issue with wild guessing.
Sorry, but: No .dae file == Limited help.
|
- Date: 2010-11-24 18:52
- Sender: Brecht Van Lommel
- Of course it matters what is wrong with your particular data, how are we supposed to guess what kind of malformed .dae input is causing the crash?
Logging is not going to fix it, if whoever wrote the code knew it was going to crash with a particular input, they would have fixed it, not added a log messages saying it's going to crash on this line.
|
- Date: 2010-11-24 20:33
- Sender: Dusan Maliarik
- Right. I attached one file that causes crash with following output (that file is not valid COLLADA 1.4.1):
$ Desktop/blender-2.55-beta-linux-glibc27-i686/blender
found bundled python: /home/skrat/Desktop/blender-2.55-beta-linux-glibc27-i686/2.55/python
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct NULL not valid
Aborted
|
|
|
- Date: 2011-09-27 16:25
- Sender: Dusan Maliarik
- Another one that crashes Blender : Version 2.59 (2.59, 2011-Aug-16) MacOS X 10.6.6
|
|
